Singapore · Singapore Completed: Apr 16, 2026 17:49 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 67 / 100
Based on 8 categories, 0 sections
Room to improve — your 10.8s load time is above Google's 2.5s 'Good' threshold.
Good foundation, but a few gaps could be exploited.
Major barriers for users with disabilities — up to 15% of your audience.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
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.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
HSTS header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 14.7 MB (8.8 MB transferred)
Performance issues directly impact user engagement and conversion rates.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/3737e093-4d38-4825-a44b-c65291733198)<a href="https://beavercheck.com/results/3737e093-4d38-4825-a44b-c65291733198"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fieee.org" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fieee.orgThis badge auto-updates with your latest scan result.
Your site has several issues that may be affecting user experience and business outcomes. Your LCP of 10.8s 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.
9 barrier(s) likely increasing bounce by ~38%.
Page takes 10.8s to load
+12% bounceUsers abandon at ~3s — you're 8.3s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 5.3s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No HSTS header
+1% bounceReturning 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% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
No viewport meta tag
+15% bounceMobile browsers render at desktop width and shrink — text unreadable, tap targets miniature
Fix: Add <meta name="viewport" content="width=device-width, initial-scale=1">
No Open Graph tags
+2% bounceLinks 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% bounceNo 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% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
No skip-to-content link
+1% bounceKeyboard 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.
$500 investment → $4,561/month returns + USD 157,500 risk avoided
$500
5h · 5 findings
$4,561 /mo
~$54,732 / year
USD 157,500
if kept compliant
$150 — 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.
5.0 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,127 / month at risk
~$157,526 / year if left unfixed
$157,500
+5 more
$2.21 /mo
27587.7 MB/mo × 0.080 USD/GB
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.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
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
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
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.
5.39 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.85 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
5.30 s
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.
9.53 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.
25.59 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
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.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
An artistic rendering of binary code moving through an electric blue cable. div.outer-wrapper > div.image-container > div.f--field > img | /sites/default/files/styles/16_9_768x432/public/dam/lrdx2... | 51.7 KiB | 35.0 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_637x359/public/dam/vxiue... | 56.4 KiB | 24.2 KiB |
div.card > div.f--field > picture > img div.card > div.f--field > picture > img | /sites/default/files/styles/9_16_540x960/public/dam/ejnc4... | 65.7 KiB | 23.9 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_637x359/public/dam/asoas... | 45.8 KiB | 8.6 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_637x359/public/dam/jwhab... | 38.8 KiB | 6.6 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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| ieee.org/ | 1.4 s |
| www.ieee.org/ | 3.6 s |
| www.ieee.org/ | 0.0 ms |
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.ieee.org/ | 713 ms |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/default/files/css/css_3DvgFGadp5NUrykuU7azDfJ8-UTu... | 49.2 KiB | 43.5 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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 reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 6.8 s |
| Script Parsing & Compilation | 1.2 s |
| Other | 1.2 s |
| Style & Layout | 575 ms |
| Garbage Collection | 289 ms |
| Parse HTML & CSS | 190 ms |
| Rendering | 101 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
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js | 5.1 KiB | 2.3 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
IEEE Logo div.footer-logo > div.f--field > a > img.lazyload |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.content-pages > iframe#myframe body.content-pages > iframe#myframe |
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.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Explore industry connections div.swiper-slide > div.links-container > div.f--field > a.link |
READ THE FULL ARTICLE div.slide-left > div.links-container > div.f--field > a.link |
SEE HOW IEEE HELPS RAISE THE WORLD'S STANDARDS div.slide-left > div.links-container > div.f--field > a.link |
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| burp/favicon.ico | Automatically upgraded to HTTPS |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | /TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 129, col 229 |
| Unload event listeners are deprecated and will be removed. | /TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 148, col 446 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
www.ieee.org/ line 5052, col 0 | Access to fetch at 'https://securesso.ieee.org/ieeevendorsso/rest/auth/validatePFToken?_=1776361720400' from origin 'https://www.ieee.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. |
www.ieee.org/ line 200, col 32 | Error: TypeError: Failed to fetch
at https://www.ieee.org/:190:7 |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_NAME_NOT_RESOLVED | |
Failed to load resource: the server responded with a status of 404 () | |
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 567, col 269 | Not allowed to load local resource: chrome://rumola/content/rumola48.png |
www.ieee.org/ line 161, col 6 | ReferenceError: cntrUpTag is not defined
at https://www.ieee.org/:162:7 |
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.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
| Content security policy |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Industry-standard audits powered by Google Lighthouse. — Desktop
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.
2.45 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
2.65 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
636 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.008
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.40 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.
6.34 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
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.
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.
Performance issues directly impact user engagement and conversion rates.
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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| /seeds/31514831/assets/asset-view/2/0/7/0/20704fef-8c54-4... | 0.0 ms | 5.4 MiB |
| app-ab24.marketo.com/js/forms2/js/forms2.min.js | 14400.0 s | 67.5 KiB |
| www.google-analytics.com/analytics.js | 7200.0 s | 20.9 KiB |
| /TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... | 86400.0 s | 34.2 KiB |
| cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano-ui.js | 86400.0 s | 30.9 KiB |
| tags.tiqcdn.com/utag/travelers/thirdparty-us/prod/utag.js | 300.0 s | 10.1 KiB |
| tags.srv.stackadapt.com/events.js | 5.0 s | 8.1 KiB |
| s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js | 0.0 ms | 5.5 KiB |
| /utag/travelers/thirdparty-us/prod/utag.3.js?utv=ut4.46.2... | 300.0 s | 5.1 KiB |
| /utag/travelers/thirdparty-us/prod/utag.5.js?utv=ut4.46.2... | 300.0 s | 3.4 KiB |
| /utag/travelers/thirdparty-us/prod/utag.4.js?utv=ut4.46.2... | 300.0 s | 3.3 KiB |
| up.pixel.ad/assets/up.js?um=1 | 0.0 ms | 3.1 KiB |
| /utag/travelers/thirdparty-us/prod/utag.2.js?utv=ut4.46.2... | 300.0 s | 1.9 KiB |
| cookie-consent.ieee.org/ieee-cookie-banner.css | 0.0 ms | 1007 B |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
A blue graphic with geometric shapes, and the number 7 million in the middle. div.inner-wrapper > div.image-container > div.f--field > img | /sites/default/files/styles/4_3_1536x1152/public/dam/qpus... | 222.6 KiB | 198.4 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_480x270/public/dam/vxiue... | 34.3 KiB | 18.1 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_480x270/public/dam/asoas... | 30.3 KiB | 14.0 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_480x270/public/dam/jwhab... | 25.4 KiB | 9.1 KiB |
div.cards-container > div.card > div.f--field > img div.cards-container > div.card > div.f--field > img | /sites/default/files/styles/16_9_480x270/public/dam/1podk... | 21.5 KiB | 5.3 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| ieee.org/ | 896 ms |
| www.ieee.org/ | 468 ms |
| www.ieee.org/ | 0.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.
Performance issues directly impact user engagement and conversion rates.
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.
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /sites/default/files/css/css_3DvgFGadp5NUrykuU7azDfJ8-UTu... | 49.2 KiB | 40.7 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
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 reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.9 s |
| Script Parsing & Compilation | 308 ms |
| Other | 289 ms |
| Style & Layout | 158 ms |
| Garbage Collection | 66 ms |
| Parse HTML & CSS | 47 ms |
| Rendering | 21 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
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js | 5.1 KiB | 2.3 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
IEEE Logo div.footer-logo > div.f--field > a > img.lazyload |
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.content-pages > iframe#myframe body.content-pages > iframe#myframe |
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.
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Industry Professionals
Authors & Researchers
Students & Young Professionals
Vol… div.content-pane-container > div.left > div.pagination-wrapper > ul.interactive-content-pane-pagination |
Cybersecurity
Simulations div.people-featured-container > div.top > div.pagination-wrapper > ul.people-feature-pagination |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Explore industry connections div.swiper-slide > div.links-container > div.f--field > a.link |
READ THE FULL ARTICLE div.slide-left > div.links-container > div.f--field > a.link |
SEE HOW IEEE HELPS RAISE THE WORLD'S STANDARDS div.slide-left > div.links-container > div.f--field > a.link |
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Performance issues directly impact user engagement and conversion rates.
| Insecure URL | Request Resolution |
|---|---|
| burp/favicon.ico | Automatically upgraded to HTTPS |
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | /TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 129, col 229 |
| Unload event listeners are deprecated and will be removed. | /TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 148, col 446 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Access to fetch at 'https://securesso.ieee.org/ieeevendorsso/rest/auth/validatePFToken?_=1776361748233' from origin 'https://www.ieee.org' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. | |
www.ieee.org/ line 200, col 32 | Error: TypeError: Failed to fetch
at https://www.ieee.org/:190:7 |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_CONNECTION_REFUSED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_FAILED | |
Failed to load resource: net::ERR_NAME_NOT_RESOLVED | |
Failed to load resource: the server responded with a status of 404 () | |
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd... line 567, col 269 | Not allowed to load local resource: chrome://rumola/content/rumola48.png |
www.ieee.org/ line 161, col 6 | ReferenceError: cntrUpTag is not defined
at https://www.ieee.org/:162:7 |
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.
Performance issues directly impact user engagement and conversion rates.
| Issue type |
|---|
| Mixed content |
| Content security policy |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
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.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
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.
Send Feedback