Skip to content
Audit Complete

Results for https://iec.ch

Visit site
CH · CHF (CHF) · Estimated Applicable regulations: nDSG/FADP Dev cost: CHF 130/hr How jurisdiction is detected
Spain Spain · Madrid Completed: Apr 22, 2026 21:43 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
D69

Site Health

Score: 69 / 100

Based on 8 categories, 0 sections

Decent speed, but optimizing further could improve engagement.

Several missing protections leave your users and data exposed.

Several issues make your site difficult for assistive technology users.

Solid SEO basics — a few optimizations could boost rankings.

Solid infrastructure — fast server responses across the board.

Several regulatory requirements are not yet met.

Missing metadata means poor previews on social media and search.

Heavier than average — reducing page weight saves energy and bandwidth.

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

How the composite score is calculated

How you compare

Amazon Route 53 · 961 peers
You 69
·
Avg 72
At average
0 50 100
Better than 9% of Amazon Route 53 sites See full Amazon Route 53 benchmark →
Apple · 1200 peers
You 69
·
Avg 72
At average
0 50 100
Better than 7% of Apple sites See full Apple benchmark →

Top Priorities (5)

1

Content-Security-Policy header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
2

HSTS header is missing

Security gaps expose your site and users to attacks, eroding trust.

Security › Security Headers
3

No Content-Security-Policy header found

Security gaps expose your site and users to attacks, eroding trust.

Security › Content Security Policy
4

Page weighs 28.8 MB (25.6 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
5

No <main> landmark found

Accessibility issues exclude users with disabilities — up to 15% of your potential audience.

Accessibility › Landmark Structure
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

3

High impact, low effort — start here.

Strategic

2

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fiec.ch)](https://beavercheck.com/results/5e444f24-1977-4346-990e-13aa701dbbb1)
<a href="https://beavercheck.com/results/5e444f24-1977-4346-990e-13aa701dbbb1"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fiec.ch" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fiec.ch

This badge auto-updates with your latest scan result.

What fixing these means

Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 77.7s exceeds Google's 2.5s 'Good' threshold and the 1 performance issue below directly contributes to it. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.

3 security gaps detected — browsers may warn visitors about your site.
Your LCP is 77.7s — fixing the 1 performance critical could bring it under Google's 2.5s 'Good' threshold.
1 accessibility issue excludes users who rely on assistive technology.
C
Could reach Estimate based on resolving critical issues

Conversion Barriers

2 critical 7 warning

9 barrier(s) likely increasing bounce by ~36%.

Speed (2)

Page takes 77.7s to load

+12% bounce

Users abandon at ~3s — you're 75.2s over the 2.5s threshold

Fix: Optimize render-blocking resources, preload the hero image, and compress images

High main-thread blocking time

+2% bounce

Page is non-interactive for 494ms after first paint

Fix: Defer third-party scripts and split large bundles

Trust (2)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

Fix: Set Strict-Transport-Security: max-age=31536000; includeSubDomains

No Content-Security-Policy header

+1% bounce

Higher XSS blast radius — one compromised script can exfiltrate the checkout form

Fix: Ship a reporting-only CSP first, then enforce once violations are clean

Usability (1)

No viewport meta tag

+15% bounce

Mobile browsers render at desktop width and shrink — text unreadable, tap targets miniature

Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">

Content (3)

No Open Graph tags

+2% bounce

Links shared on LinkedIn / Slack / Facebook show bare URLs — referral clicks drop

Fix: Add og:title, og:description, og:image, og:url to the page head

No structured data

+2% bounce

No rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices

Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)

Thin content

+3% bounce

Under 300 words — visitors bounce looking for substance, search engines rank competitors first

Fix: Add a substantive FAQ, product detail, or case-study section

Navigation (1)

No skip-to-content link

+1% bounce

Keyboard and screen-reader users must tab through the entire header on every page

Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element

Preliminary CRO audit — each barrier links to the tab with detailed analysis.

Return on Investment

CHF 650 investment → CHF 5.69/month returns + CHF 250,000 risk avoided

Payback period: > 2 years First-year ROI: -89%

Investment

CHF 650

5h · 5 findings

Monthly returns

CHF 5.69 /mo

~CHF 68 / year

  • Bandwidth savings CHF 5.69

Regulatory risk avoided

CHF 250,000

if kept compliant

  • nDSG/FADP CHF 250,000

CHF 195 — in quick wins — start here for the fastest payback

Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.

Full methodology & sources

Estimated Remediation Cost

CHF650

5.0 developer hours at CHF130/hr

Based on Switzerland rates (CHF130/hr)

Quick wins
CHF195 3 fixes in ~90 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions
CHF /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

CHF 20,839 / month at risk

~CHF 250,068 / year if left unfixed

Compliance Risk

CHF 250,000

nDSG/FADP
  • No privacy policy link detected
    nDSG/FADP: CHF 1,000 – CHF 250,000
  • Trackers detected but no cookie policy found
    nDSG/FADP: CHF 1,000 – CHF 250,000
  • Trackers detected but no privacy policy found
    nDSG/FADP: CHF 1,000 – CHF 250,000

+1 more

Bandwidth Waste

CHF 5.69 /mo

80431.6 MB/mo × 0.071 CHF/GB

  • Optimize transfer: save ~8.0 MB per page load
    Saves CHF 5.69/mo

Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

potential monthly revenue
Current bounce (est.)
After fixes (est.)
Estimated bounce reduction

Fix 5 critical issues to capture this value

How this is calculated

Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

Your data stays in your browser — nothing is sent to our servers

Was this report useful?

Thanks for your feedback!

We'll use a cached audit if available, or offer to scan.

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

42
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
81
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
75
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience.

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

10.43 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

77.65 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

494 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.007

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

17.24 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

79.25 s

Detailed Report

Audit breakdown by category with detailed findings.

42

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:48.728 source:map[column:197 line:809 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-3F71XQS4K3 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:48.728 source:map[column:55 line:806 type:source-location url:https://www.googletagmanager.com/gtag/js?id=G-3F71XQS4K3 urlProvider:network]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: Shaping the future of standards Explore tools for inclusive standards and parti…
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,SECTION,2,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,A,0,DIV,0,DIV
selector: div.col > a > div.paragraph > div.wrapper
snippet: <div class="wrapper" style="background-image: url(&quot;/system/files/styles/original_image/private/2026-03/i…&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
iec.ch/themes/custom/iec/images/arrow-right-simple-line-icons.png5.7 KiB5.4 KiB
subscribe div.field > p.text-align-center > a > img
iec.ch/system/files/inline-images/subscribe_darkblue.png6.2 KiB5.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 821 ms
URLTime Spent
iec.ch/821 ms
iec.ch/0.0 ms
iec.ch/homepage0.0 ms

The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.2 s
Other394 ms
Script Parsing & Compilation307 ms
Style & Layout289 ms
Parse HTML & CSS90 ms
Rendering22 ms
Garbage Collection9.4 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Home div.visible-xs-block > div.iec-logo-header > a.visible-xs-block > img
iec.ch/themes/custom/iec/images/iec-logo-mobile.svg
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
iec.ch/themes/custom/iec/images/arrow-right-simple-line-icons.png
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
iec.ch/themes/custom/iec/images/arrow-right-simple-line-icons.png
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
iec.ch/themes/custom/iec/images/arrow-right-simple-line-icons.png
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
iec.ch/themes/custom/iec/images/arrow-right-simple-line-icons.png
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
logo div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-icon > img.b-lazy
logo div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-icon > img.b-lazy
logo div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-icon > img.b-lazy
logo div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-icon > img.b-lazy

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 5 user timings
JavaScript execution time 1.2 s
Avoid long main-thread tasks 11 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 100 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 110 ms
Avoid large layout shifts 2 layout shifts found
INP breakdown
Avoid non-composited animations
81

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We use cookies on this site to enhance your user experience By clicking the Ac… body.path-node > div#sliding-popup

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Past two weeks list section#single-element-text-7837 > div.text-link-container > div.item-link > a.hvr-icon-forward
Final Draft International Standards div.text-block-content > div.field > p > a
See details  section#single-element-text-7839 > div.text-link-container > div.item-link > a.hvr-icon-forward
Visit here section#single-element-text-3592 > div.text-link-container > div.item-link > a.hvr-icon-forward
Energy a > div.paragraph > div.iec-slide-item-title > div.field
Healthcare a > div.paragraph > div.iec-slide-item-title > div.field
SDGs a > div.paragraph > div.iec-slide-item-title > div.field
Cities & Communities a > div.paragraph > div.iec-slide-item-title > div.field
Climate action a > div.paragraph > div.iec-slide-item-title > div.field
Cyber security a > div.paragraph > div.iec-slide-item-title > div.field
Smart manufacturing a > div.paragraph > div.iec-slide-item-title > div.field
Transportation a > div.paragraph > div.iec-slide-item-title > div.field
Industry a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Government and regulators a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Developing countries a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Academia a > div.iec-for-all-item-content > div.icon-text-wrapper > div.iec-for-all-item-title
Read more div.iec-white-papers-slider-item > article.document > div.iec-document-card-read-more-container > a.iec-read-more
Read more div.iec-white-papers-slider-item > article.document > div.iec-document-card-read-more-container > a.iec-read-more
Please select the services that are of interest to you, and stay up to date wit… div.cs-container > div.iec-block-container > div.col-sm-12 > h2.block-subtitle
Details about our newsletters div.iec-block-container > div.block-readmore > div.field > a

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-iframe
div.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-iframe

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.slides-container > div.iec-white-papers-slider-item > article.document > a div.slides-container > div.iec-white-papers-slider-item > article.document > a
div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook
div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin
div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
countries div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
standards div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
certificates div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
experts div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title

These are opportunities to improve keyboard navigation in your application.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
75

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img
a > div.iec-for-all-item-content > div.iec-for-all-item-link > img a > div.iec-for-all-item-content > div.iec-for-all-item-link > img

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

78
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
79
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
100
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
83
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

Key metrics that affect user experience. — Desktop

First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.

1.44 s

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

2.80 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

24 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.012

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

1.80 s

Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.

3.66 s

Detailed Report

Audit breakdown by category with detailed findings.

78

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling

Why this matters

Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.

Learn more

Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.

Source: Google web.dev / Lighthouse

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Consider setting font-display to swap or optional to ensure text is consistently visible. swap can be further optimized to mitigate layout shifts with font metric overrides.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:62.416 source:map[type:text value:[unattributed]]]]

Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-DIV
nodeLabel: Shaping the future of standards Explore tools for inclusive standards and parti…
path: 1,HTML,1,BODY,2,DIV,1,DIV,0,DIV,0,SECTION,2,DIV,0,ARTICLE,0,DIV,0,DIV,0,DIV,0,DIV,0,SECTION,0,DIV,0,DIV,0,A,0,DIV,0,DIV
selector: div.col > a > div.paragraph > div.wrapper
snippet: <div class="wrapper" style="background-image: url(&quot;/system/files/styles/original_image/private/2026-03/i…&quot;);">

Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.

Why this matters

Performance issues directly impact user engagement and conversion rates.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates

Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
Energy a > div.paragraph > div.iec-slide-item-title > div.field
/2026-03/professional_photo-liu_haibo.jpg?VersionId=0EJqh...14.7 MiB11.2 MiB
0 div.field--item > div.paragraph > div.iec-statistics-block-item-container > h1#iec-count-up-1905772950
/2026-04/adobestock_1052088146.jpeg?VersionId=zxk3C36Ycua...5.9 MiB732.9 KiB
Home div#navbar-collapse > div.region > a.hidden-xs > img
iec.ch/themes/custom/iec/images/IEC_logo.jpg22.7 KiB20.5 KiB
subscribe div.field > p.text-align-center > a > img
iec.ch/system/files/inline-images/subscribe_darkblue.png6.2 KiB5.1 KiB

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 275 ms
URLTime Spent
iec.ch/275 ms
iec.ch/0.0 ms
iec.ch/homepage0.0 ms

Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.

Why this matters

Multi-megabyte JavaScript bundles delay every interactive feature on the page.

Learn more

This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.

Source: Google web.dev / Lighthouse

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failure reasonFailure type
The page has an unload handler in a sub frame.Actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL
Home div#navbar-collapse > div.region > a.hidden-xs > img
iec.ch/themes/custom/iec/images/IEC_logo.jpg
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
icon a > div.paragraph > div.iec-slide-item-img-wrap > img.iec-slide-item-img
logo div.iec-for-all-item-container > div.iec-for-all-item-flex-item > div.iec-for-all-item-img > img.b-lazy
logo div.iec-for-all-item-container > div.iec-for-all-item-flex-item > div.iec-for-all-item-img > img.b-lazy
logo div.iec-for-all-item-container > div.iec-for-all-item-flex-item > div.iec-for-all-item-img > img.b-lazy
logo div.iec-for-all-item-container > div.iec-for-all-item-flex-item > div.iec-for-all-item-img > img.b-lazy

More information about the performance of your application. These numbers don't directly affect the Performance score.

Max Potential First Input Delay 100 ms
Layout shift culprits
Optimize DOM size
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 5 user timings
JavaScript execution time 0.3 s
Minimizes main-thread work 0.8 s
Avoid long main-thread tasks 2 long tasks found
Network Requests
Network Round Trip Times 100 ms
Server Backend Latencies 90 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 80 ms
Avoid large layout shifts 10 layout shifts found
INP breakdown
Avoid non-composited animations
79

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Energy SDGs Climate action Smart manufacturing Healthcare Cities & Communities … div.container > div.iec-grid-icon-slider-wrapper > div#grid-icon-slider-497932334 > div.carousel-inner
Read more Read more Read more Read more Read more div.container > div.iec-white-papers-slider-wrapper > div#grid-icon-slider-2109212649 > div.carousel-inner
Read more Read more Read more Read more Read more div.container > div.iec-white-papers-slider-wrapper > div#grid-icon-slider-2134488651 > div.carousel-inner

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We use cookies on this site to enhance your user experience By clicking the Ac… body.path-node > div#sliding-popup

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more about input field labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Energy SDGs Climate action Smart manufacturing Healthcare Cities & Communities … div.container > div.iec-grid-icon-slider-wrapper > div#grid-icon-slider-497932334 > div.carousel-inner
Read more Read more Read more Read more Read more div.container > div.iec-white-papers-slider-wrapper > div#grid-icon-slider-2109212649 > div.carousel-inner
Read more Read more Read more Read more Read more div.container > div.iec-white-papers-slider-wrapper > div#grid-icon-slider-2134488651 > div.carousel-inner

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Advanced search ul.menu > li.first > a > span.link-text
Webstore ul.menu > li > a > span.link-text
IEC PSP nav#block-topmenu--2 > ul.menu > li > a
e-tech nav#block-topmenu--2 > ul.menu > li > a
Online learning nav#block-topmenu--2 > ul.menu > li > a
Contact us nav#block-topmenu--2 > ul.menu > li.last > a
A global network that covers 99% of the world population and offers a free prog… div.iec-statistics-block-item-container > div.hidden-xs > div.field > p
Develops international standards that represent a global concensus of state-of-… div.iec-statistics-block-item-container > div.hidden-xs > div.field > p
Four Conformity Assessment Systems that cover the breadth of electrical and ele… div.iec-statistics-block-item-container > div.hidden-xs > div.field > p
Over 30 000 experts and more than 100 years expertise div.iec-statistics-block-item-container > div.hidden-xs > div.field > p
Past two weeks list section#single-element-text-7837 > div.text-link-container > div.item-link > a.hvr-icon-forward
Final Draft International Standards div.text-block-content > div.field > p > a
See details  section#single-element-text-7839 > div.text-link-container > div.item-link > a.hvr-icon-forward
Visit here section#single-element-text-3592 > div.text-link-container > div.item-link > a.hvr-icon-forward
Energy a > div.paragraph > div.iec-slide-item-title > div.field
SDGs a > div.paragraph > div.iec-slide-item-title > div.field
Climate action a > div.paragraph > div.iec-slide-item-title > div.field
Smart manufacturing a > div.paragraph > div.iec-slide-item-title > div.field
Healthcare a > div.paragraph > div.iec-slide-item-title > div.field
Cities & Communities a > div.paragraph > div.iec-slide-item-title > div.field
Cyber security a > div.paragraph > div.iec-slide-item-title > div.field
Transportation a > div.paragraph > div.iec-slide-item-title > div.field
Industry a > div.iec-for-all-item-container > div.iec-for-all-item-flex-item > p.iec-for-all-item-title
Government and regulators a > div.iec-for-all-item-container > div.iec-for-all-item-flex-item > p.iec-for-all-item-title
Developing countries a > div.iec-for-all-item-container > div.iec-for-all-item-flex-item > p.iec-for-all-item-title
Academia a > div.iec-for-all-item-container > div.iec-for-all-item-flex-item > p.iec-for-all-item-title
Please select the services that are of interest to you, and stay up to date wit… div.cs-container > div.iec-block-container > div.col-sm-12 > h2.block-subtitle
Details about our newsletters div.iec-block-container > div.block-readmore > div.field > a

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-iframe
div.text-block-content > div.field > p > iframe.fw-iframe div.text-block-content > div.field > p > iframe.fw-iframe

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.row > div.iec-white-papers-slider-item > article.document > a div.row > div.iec-white-papers-slider-item > article.document > a
div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook div.paragraph > ul.social-media-links--platforms > li > a.iec-facebook
div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin div.paragraph > ul.social-media-links--platforms > li > a.iec-linkedin
div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel div.paragraph > ul.social-media-links--platforms > li > a.iec-youtube_channel

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
countries div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
standards div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
certificates div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title
experts div.field--item > div.paragraph > div.iec-statistics-block-item-container > h3.iec-statistics-block-item-title

These are opportunities to improve keyboard navigation in your application.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
Form elements have associated labels
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
100

Best Practices

Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
No browser errors logged to the console
No issues in the `Issues` panel in Chrome Devtools
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Page has valid source maps
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
83

SEO

These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Crawling and Indexing

Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item div.region > div.visible-xs-block > div.iec-top-menu-container > a.iec-mobile-top-menu-item

To appear in search results, crawlers need access to your app.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`
robots.txt is valid

Send Feedback