C — https://theiet.org | BeaverCheck Audit

Site Health

Score: 75 / 100

Based on 8 categories, 0 sections

Fast site — your users get a smooth experience.

Several missing protections leave your users and data exposed.

Major barriers for users with disabilities — up to 15% of your audience.

Well-optimized for search — your content is discoverable.

Good server performance with room for optimization.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

Lean and efficient — low environmental impact per visit.

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

Apple · 1212 peers

You 75

Avg 72

At average

0 50 100

Better than 70% of Apple sites See full Apple benchmark →

Boomerang · 151 peers

You 75

Avg 71

At average

0 50 100

Better than 86% of Boomerang sites See full Boomerang benchmark →

Top Priorities (5)

Content-Security-Policy header is missing

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

Security › Security Headers

No Content-Security-Policy header found

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

Security › Content Security Policy

6 image(s) missing alt attribute

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

Accessibility › Alt Text Quality

6 image-in-link without alt text

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

Accessibility › Alt Text Quality

6 image-only link(s) without alt text

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

Accessibility › Link & Button Quality

View fix priority matrix

Fix Priority Matrix

5 findings

Impact

Quick Wins

High impact, low effort — start here.

Strategic

High impact, requires investment.

Easy Improvements

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Ftheiet.org)](https://beavercheck.com/results/77490474-6785-4b5e-88c7-8a69acd110b5)

HTML

<a href="https://beavercheck.com/results/77490474-6785-4b5e-88c7-8a69acd110b5"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Ftheiet.org" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Ftheiet.org

This badge auto-updates with your latest scan result.

What fixing these means

Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. 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.

2 security gaps detected — browsers may warn visitors about your site.

3 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

6 warning

6 barrier(s) likely increasing bounce by ~13%.

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

Content (2)

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, …)

Content is hard to read

+2% bounce

Graduate-level reading difficulty — limits the addressable audience for product or blog pages

Fix: Shorten sentences; replace jargon with plain language; target Flesch ease ≥60

Navigation (2)

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

1 broken link(s) on the page

+2% bounce

Clicks land on 404s — trust drops and the session often ends

Fix: Fix or remove the broken destinations surfaced on the Content tab

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

Return on Investment

£413 investment → £0.13/month returns + GBP 50,000 risk avoided

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

Investment

£413

6h · 5 findings

Monthly returns

£0.13 /mo

~£1.59 / year

Bandwidth savings £0.13

Regulatory risk avoided

GBP 50,000

if kept compliant

Equality Act 2010 GBP 50,000

£75 — 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

£413

5.5 developer hours at £75/hr

Based on United Kingdom rates (£75/hr)

Quick wins

£75 2 fixes in ~60 minutes

Start here for the best return on investment

Cost by category

Cost by effort level

Adjust assumptions

Custom rate

£ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

£4,167 / month at risk

~£50,002 / year if left unfixed

Compliance Risk

£50,000

Equality Act 2010

2 of 3 <nav> elements are unlabeled
Equality Act 2010: GBP 500 – GBP 50,000
Skip navigation link is missing (WCAG 2.4.1)
Equality Act 2010: GBP 500 – GBP 50,000
6 image(s) missing alt attribute
Equality Act 2010: GBP 500 – GBP 50,000

+3 more

Bandwidth Waste

£0.13 /mo

2105.4 MB/mo × 0.063 GBP/GB

Optimize transfer: save ~211 KB per page load
Saves £0.13/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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

SEO

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.

0 ms

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

0 ms

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

0 ms

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

0.000

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

0 ms

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

0 ms

Detailed Report

Audit breakdown by category with detailed findings.

—

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.

Request	Cache TTL	Transfer Size
js.hcaptcha.com/1/api.js	300.0 s	86.0 KiB

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.

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

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.

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.

Diagnostics

Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn how to avoid long main-thread tasks

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 reason	Failure type
Pages with cache-control:no-store header cannot enter back/forward cache.	Actionable

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

●Layout shift culprits

●Optimize DOM size

●Font display

●Forced reflow

●Improve image delivery

●Modern HTTP

●Network dependency tree

●Render blocking requests

●Optimize viewport for mobile

●Avoids enormous network payloads Total size was 685 KiB

●JavaScript execution time 0.3 s

●Minimizes main-thread work 0.7 s

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 50 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 10 ms

○INP breakdown

○LCP breakdown

○LCP request discovery

○User Timing marks and measures

○Avoid non-composited animations

○Avoid large layout shifts

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.

Names and labels

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

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
body > iframe#main-iframe `body > iframe#main-iframe`

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.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These are opportunities to improve the interpretation of your content by users in different locales.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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-hidden="true"]` is not present on the document `<body>`

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA attributes are used as specified for the element's role

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

○`[role]`s have all required `[aria-*]` attributes

○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

○`[role]` values are valid

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○Buttons have an accessible name

○The page contains a heading, skip link, or landmark region

○Background and foreground colors have a sufficient contrast ratio

○`<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

○Heading elements appear in a sequentially-descending order

○`<html>` element has a valid value for its `[lang]` attribute

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Image elements have `[alt]` attributes

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Form elements have associated labels

○Links are distinguishable without relying on color.

○Links have a discernible name

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○No element has a `[tabindex]` value greater than 0

○Touch targets have sufficient size and spacing.

○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.

○Identical links have the same purpose.

○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.

Best Practices

Browser Compatibility

Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration.

Why this matters

Performance issues directly impact user engagement and conversion rates.

A character encoding declaration is required. It can be done with a `<meta>` tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header. Learn more about declaring the character encoding.

Why this matters

Performance issues directly impact user engagement and conversion rates.

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Fledge	js.hcaptcha.com/1/api.js line 3, col 47111

●Uses HTTPS

●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

●No browser errors logged to the console

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●Ensure proper origin isolation with COOP

●Mitigate clickjacking with XFO or CSP

●Mitigate DOM-based XSS with Trusted Types

●Page has valid source maps

○Redirects HTTP traffic to HTTPS

○Detected JavaScript libraries

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.

Crawling and Indexing

Search engines are unable to include your pages in search results if they don't have permission to crawl them. Learn more about crawler directives.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Blocking Directive Source
`head > meta`

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

Content Best Practices

The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more about document titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

○Structured data is valid

●Page has successful HTTP status code

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

○Image elements have `[alt]` attributes

○Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

Performance

Accessibility

Best Practices

SEO

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.

788 ms

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

2.45 s

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

90 ms

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

0.254

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

1.85 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.

2.52 s

Detailed Report

Audit breakdown by category with detailed findings.

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.

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 ▾

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.

Request	Cache TTL	Transfer Size
www.theiet.org/Themes/base/js/index-faeb5270.js	0.0 ms	43.1 KiB
www.theiet.org/Themes/base/css/styles.min.css?v=13.3.0	0.0 ms	42.4 KiB
js.monitor.azure.com/scripts/b/ai.2.min.js	1800.0 s	46.2 KiB
www.theiet.org/Themes/base/js/index-05f4331b.js	0.0 ms	37.7 KiB
/uc.js?cbid=32853404-389a-468c-95fb-79ebc39057ef&implemen...	980.0 s	27.0 KiB
ietp-web-app-global-assets.azurewebsites.net/media/pfqdy5jk/weibo-icon.png	0.0 ms	24.0 KiB
rum-agent.na-01.cloud.solarwinds.com/ra-e-1780603686429937664.js	14400.0 s	27.0 KiB
www.theiet.org/Themes/base/js/main.js?v=13.3.0	0.0 ms	9.4 KiB
/media/p2mdmbxp/web_low-angle-view-crowded-residential-to...	604800.0 s	87.2 KiB
static.responsetap.com/static/scripts/inf_76.js?h=5723774165a404c2c59c	3600.0 s	10.1 KiB
www.theiet.org/Themes/base/js/iet-main-navigation.entry.js	0.0 ms	7.5 KiB
ietp-web-app-global-assets.azurewebsites.net/media/13ghi50o/wechat-icon.png	0.0 ms	7.1 KiB
www.theiet.org/Themes/base/js/cmstoolkit-components.esm.js	0.0 ms	5.1 KiB
www.theiet.org/Themes/base/js/iet-button.entry.js	0.0 ms	4.8 KiB
/media/24nnk1mj/one-of-the-hydrogen-powered-generators.jp...	604800.0 s	47.9 KiB
www.theiet.org/Themes/base/js/iet-cta-full-width.entry.js	0.0 ms	4.7 KiB
www.theiet.org/Themes/base/js/iet-button-collection.entry.js	0.0 ms	4.7 KiB
/media/5grcdsl2/cpd-advisors.png?format=webp&quality=80&w...	604800.0 s	45.6 KiB
www.theiet.org/Themes/base/js/iet-secondary-navigation.entry.js	0.0 ms	4.5 KiB
/media/10985/group-of-people-looking-at-a-device.jpg?form...	604800.0 s	44.0 KiB
/media/wrilgzyb/safer-homes.png?format=webp&quality=80&wi...	604800.0 s	43.7 KiB
www.theiet.org/Themes/base/js/iet-global-bar.entry.js	0.0 ms	3.7 KiB
www.theiet.org/Themes/base/js/iet-copy-module.entry.js	0.0 ms	3.4 KiB
www.theiet.org/Themes/base/js/iet-cta.entry.js	0.0 ms	3.3 KiB
www.theiet.org/Themes/base/js/iet-global-bar.service-d990708d.js	0.0 ms	2.8 KiB
www.theiet.org/Themes/base/js/iet-user-panel.entry.js	0.0 ms	2.7 KiB
/media/ql0ewqvb/happy-agronomist-standing-with-laptop-in-...	604800.0 s	26.8 KiB
www.theiet.org/Themes/base/js/iet-homepage-banner.entry.js	0.0 ms	2.6 KiB
www.theiet.org/Themes/base/js/iet-site-header.entry.js	0.0 ms	2.5 KiB
/media/10112/one-to-one-support-cropped.jpg?format=webp&q...	604800.0 s	25.2 KiB
www.theiet.org/Themes/base/js/iet-global-search.entry.js	0.0 ms	2.5 KiB
ietp-web-app-global-assets.azurewebsites.net/media/2zycdsf5/instagram.svg	0.0 ms	2.1 KiB
www.theiet.org/Themes/base/js/iet-media-item.entry.js	0.0 ms	2.1 KiB
/media/rzkmovpa/cta_6x4_03.webp?format=webp&quality=80&wi...	604800.0 s	17.6 KiB
/media/2uao1mok/iet_engx_icon_dark_background.svg	0.0 ms	1.5 KiB
ietp-web-app-global-assets.azurewebsites.net/media/tfqfqayy/linkedin.svg	0.0 ms	1.3 KiB
/media/2563/untitled-7.jpg?format=webp&quality=80&width=4...	604800.0 s	12.9 KiB
ietp-web-app-global-assets.azurewebsites.net/media/xkxkxlst/youtube.svg	0.0 ms	1.3 KiB
www.theiet.org/Themes/base/js/element.service-647e64ad.js	0.0 ms	821 B
www.theiet.org/Themes/base/js/constants-714418d0.js	0.0 ms	655 B
www.theiet.org/Themes/base/js/app-globals-0f993ce5.js	0.0 ms	311 B
/p.css?s=1&k=eag8ezh&ht=tk&f=15528.15530.17252.17253&a=14...	604800.0 s	172 B

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]

items: [map[node:map[type:text value:Total] score:0.253854] map[node:map[boundingRect:map[bottom:4412 height:4119 left:0 right:1350 top:293 width:1350] lhId:page-7-MAIN nodeLabel:Start of main content Working to engineer a better world We inspire, inform an… path:1,HTML,1,BODY,7,MAIN selector:body.other-browser > main.row snippet:<main class="row"> type:node] score:0.183546 subItems:map[items:[map[cause:Unsized image element extra:map[boundingRect:map[bottom:183 height:83 left:15 right:433 top:100 width:418] lhId:page-4-IMG nodeLabel:IET logo - link to site homepage path:1,HTML,1,BODY,6,HEADER,0,IET-SITE-HEADER,1,DIV,0,A,0,DIV,0,IET-MEDIA-ITEM,1,PICTURE,1,IMG selector:div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item snippet:<img class="sc-iet-media-item sc-iet-site-header" loading="lazy" src="/media/2563/untitled-7.jpg?format=webp&quality=80&width=419&height=83&v=1d…" alt="IET logo - link to site homepage"> type:node]]] type:subitems]] map[node:map[boundingRect:map[bottom:4412 height:4119 left:0 right:1350 top:293 width:1350] lhId:page-7-MAIN nodeLabel:Start of main content Working to engineer a better world We inspire, inform an… path:1,HTML,1,BODY,7,MAIN selector:body.other-browser > main.row snippet:<main class="row"> type:node] score:0.043588] map[node:map[boundingRect:map[bottom:4412 height:4119 left:0 right:1350 top:293 width:1350] lhId:page-7-MAIN nodeLabel:Start of main content Working to engineer a better world We inspire, inform an… path:1,HTML,1,BODY,7,MAIN selector:body.other-browser > main.row snippet:<main class="row"> type:node] score:0.02672]]

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:50.055 source:map[column:15 line:3007 type:source-location url:https://www.theiet.org/Themes/base/js/index-faeb5270.js 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:34.306 source:map[type:text value:[unattributed]]] map[reflowTime:49.107 source:map[column:69 line:24 type:source-location url:https://www.theiet.org/Themes/base/js/element.service-647e64ad.js urlProvider:network]] map[reflowTime:0.948 source:map[column:72 line:54 type:source-location url:https://www.theiet.org/Themes/base/js/iet-main-navigation.entry.js urlProvider:network]]]

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.

	URL	Resource Size	Est Savings
div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item `div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item`	/media/p2mdmbxp/web_low-angle-view-crowded-residential-to...	86.8 KiB	66.0 KiB
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/pfqdy5jk/weibo-icon.png	23.3 KiB	23.2 KiB
div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item `div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item`	/media/24nnk1mj/one-of-the-hydrogen-powered-generators.jp...	47.7 KiB	6.9 KiB
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/13ghi50o/wechat-icon.png	6.5 KiB	6.4 KiB
IET logo - link to site homepage `div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item`	/media/2563/untitled-7.jpg?format=webp&quality=80&width=4...	10.4 KiB	4.8 KiB

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-5-IMG

nodeLabel: div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item

path: 1,HTML,1,BODY,7,MAIN,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,IET-HOMEPAGE-BANNER,1,DIV,0,IET-MEDIA-ITEM,1,PICTURE,1,IMG

selector: div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item

snippet: <img class="sc-iet-media-item sc-iet-homepage-banner" loading="lazy" src="/media/ql0ewqvb/happy-agronomist-standing-with-laptop-in-field.jpg?format=…" alt="">

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

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

Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Transfer Size	Duration
www.theiet.org/Themes/base/css/styles.min.css?v=13.3.0	42.4 KiB	120 ms
www.theiet.org/Themes/base/js/main.js?v=13.3.0	9.4 KiB
fonts.googleapis.com/icon?family=Material+Icons&display=swap	823 B	277 ms
/css2?family=Material+Symbols+Sharp:opsz,wght,FILL,GRAD@2...	449 B	57 ms
/p.css?s=1&k=eag8ezh&ht=tk&f=15528.15530.17252.17253&a=14...	172 B	210 ms
use.typekit.net/eag8ezh.css	979 B	208 ms

HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URL	Protocol
ietp-web-app-global-assets.azurewebsites.net/media/2zycdsf5/instagram.svg	http/1.1
ietp-web-app-global-assets.azurewebsites.net/media/tfqfqayy/linkedin.svg	http/1.1
ietp-web-app-global-assets.azurewebsites.net/media/xkxkxlst/youtube.svg	http/1.1
ietp-web-app-global-assets.azurewebsites.net/media/13ghi50o/wechat-icon.png	http/1.1
ietp-web-app-global-assets.azurewebsites.net/media/pfqdy5jk/weibo-icon.png	http/1.1
/media/2uao1mok/iet_engx_icon_dark_background.svg	http/1.1

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: 874 ms

URL	Time Spent
theiet.org/	203 ms
www.theiet.org/	670 ms
www.theiet.org/	0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

Why this matters

Performance issues directly impact user engagement and conversion rates.

Element	Layout shift score
Start of main content Working to engineer a better world We inspire, inform an… `body.other-browser > main.row`	0.184
Start of main content Working to engineer a better world We inspire, inform an… `body.other-browser > main.row`	0.044
Start of main content Working to engineer a better world We inspire, inform an… `body.other-browser > main.row`	0.027

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.

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 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 ▾

Source: Google web.dev / Lighthouse

Estimated savings: 210 ms 124.8 KiB

URL	Transfer Size	Est Savings
www.googletagmanager.com/gtm.js?id=GTM-N9QX7R7W	149.2 KiB	57.1 KiB
www.theiet.org/Themes/base/js/index-05f4331b.js	37.5 KiB	33.9 KiB
/32853404-389a-468c-95fb-79ebc39057ef/cc.js?renew=false&r...	105.8 KiB	33.8 KiB

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 reason	Failure type
The page has an unload handler in the main frame.	Actionable

Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 0.0 ms 57.8 KiB

URL	Transfer Size	Est Savings
www.theiet.org/Themes/base/js/index-faeb5270.js	40.7 KiB	20.6 KiB
inline: (function(){function r(e,n,t){func…	21.0 KiB	17.5 KiB
www.theiet.org/Themes/base/js/index-05f4331b.js	37.5 KiB	12.5 KiB
www.theiet.org/Themes/base/js/main.js?v=13.3.0	9.2 KiB	7.2 KiB

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.

Estimated savings: 0.0 ms 51.1 KiB

URL	Transfer Size	Est Savings
www.theiet.org/Themes/base/css/styles.min.css?v=13.3.0	39.8 KiB	38.1 KiB
.iet-global-assets .iet-purple-light-100{background-color:#9c67a8;color:#000} …	14.6 KiB	13.0 KiB

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
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/pfqdy5jk/weibo-icon.png
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/13ghi50o/wechat-icon.png
IET logo - link to site homepage `div.umb-block-list > iet-media-item.sc-iet-media-item > picture.sc-iet-media-item > img.sc-iet-media-item`	/media/2563/untitled-7.jpg?format=webp&quality=80&width=4...
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/xkxkxlst/youtube.svg
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/2zycdsf5/instagram.svg
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	ietp-web-app-global-assets.azurewebsites.net/media/tfqfqayy/linkedin.svg
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`	/media/2uao1mok/iet_engx_icon_dark_background.svg
Logo `div#ivcb-banner > div#ivcb-welcome > div.ivcb-logo > img`

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

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Optimize viewport for mobile

●Minify CSS

●Avoids enormous network payloads Total size was 1,110 KiB

●User Timing marks and measures 741 user timings

●JavaScript execution time 0.6 s

●Minimizes main-thread work 1.4 s

●Avoid long main-thread tasks 2 long tasks found

●Avoid non-composited animations 24 animated elements found

●Network Requests

●Network Round Trip Times 140 ms

●Server Backend Latencies 270 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Initial server response time was short Root document took 170 ms

○INP breakdown

Accessibility

ARIA

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Essential (344) `div#ivcb-banner > div#ivcb-welcome > div#ivcb-dec-outter > label.ivcb-dec-label-necessary`
Preferences (5) `div#ivcb-banner > div#ivcb-welcome > div#ivcb-dec-outter > label.ivcb-dec-label-preference`
Statistics (118) `div#ivcb-banner > div#ivcb-welcome > div#ivcb-dec-outter > label.ivcb-dec-label-statistics`
Marketing (111) `div#ivcb-banner > div#ivcb-welcome > div#ivcb-dec-outter > label.ivcb-dec-label-advertising`

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.

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
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`

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.

○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]` 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

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●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.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●`[lang]` attributes have a valid value

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Uses ARIA roles only on compatible elements

●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.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Elements with `role="dialog"` or `role="alertdialog"` 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

○`<frame>` or `<iframe>` elements have a title

○`<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

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace...
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/.	/_Incapsula_Resource?SWJIYLWA=5074a744e2e3d891814e9a2dace...
Unload event listeners are deprecated and will be removed.	js.monitor.azure.com/scripts/b/ai.2.min.js line 4, col 20534

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Issue type
Content security policy

●Uses HTTPS

●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

●Ensure CSP is effective against XSS attacks

●Use a strong HSTS policy

●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

○Mitigate clickjacking with XFO or CSP

SEO

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
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`
div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img `div.umb-block-grid__layout-container > div.umb-block-grid__layout-item > a.social-icon > img`

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

○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

●Links have descriptive text

●Links are crawlable

●robots.txt is valid

●Document has a valid `hreflang`

●Document has a valid `rel=canonical`

Results for https://theiet.org

Site Health

How you compare

Top Priorities (5)

Fix Priority Matrix

Quick Wins

Strategic

Easy Improvements

Deprioritize

What fixing these means

Conversion Barriers

Trust (2)

Content (2)

Navigation (2)

Return on Investment

Investment

Monthly returns

Regulatory risk avoided

Estimated Remediation Cost

Cost by category

Cost by effort level

What Inaction Is Costing You

Compliance Risk

Bandwidth Waste

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Names and labels

Internationalization and localization

Best practices

Best Practices

Browser Compatibility

General

SEO

Crawling and Indexing

Content Best Practices

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

ARIA

Names and labels

Best Practices

General

SEO

Content Best Practices

Keyboard Shortcuts