Skip to content
https://ieee.org

Lighthouse Mobile

· 0 checks — Mobile Lighthouse audit -- Performance, Accessibility, Best Practices, and SEO category breakdown.
SCORE
0
GRADE
FIX
0
REVIEW
0
PASS
0
INFO
0

Detailed Report

Audit breakdown by category with detailed findings.

27

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

Performance issues directly impact user engagement and conversion rates.

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.

RequestCache TTLTransfer Size
/seeds/31514831/assets/asset-view/2/0/7/0/20704fef-8c54-4...0.0 ms5.4 MiB
app-ab24.marketo.com/js/forms2/js/forms2.min.js14400.0 s67.5 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd...86400.0 s34.2 KiB
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano-ui.js86400.0 s30.9 KiB
tags.tiqcdn.com/utag/travelers/thirdparty-us/prod/utag.js300.0 s10.1 KiB
tags.srv.stackadapt.com/events.js5.0 s8.1 KiB
s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js0.0 ms5.5 KiB
/utag/travelers/thirdparty-us/prod/utag.3.js?utv=ut4.46.2...300.0 s5.1 KiB
/utag/travelers/thirdparty-us/prod/utag.5.js?utv=ut4.46.2...300.0 s3.5 KiB
/utag/travelers/thirdparty-us/prod/utag.4.js?utv=ut4.46.2...300.0 s3.3 KiB
up.pixel.ad/assets/up.js?um=10.0 ms3.1 KiB
/utag/travelers/thirdparty-us/prod/utag.2.js?utv=ut4.46.2...300.0 s1.9 KiB
cookie-consent.ieee.org/ieee-cookie-banner.css0.0 ms1008 B
/a?v=3&t=l&pid=660897053&rv=64f0&tag_exp=0~115616985~1159...0.0 ms11 B

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.

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-IMG
nodeLabel: An artistic rendering of binary code moving through an electric blue cable.
path: 1,HTML,1,BODY,72,DIV,2,MAIN,0,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,1,DIV,0,DIV,1,DIV,0,IMG
selector: div.outer-wrapper > div.image-container > div.f--field > img
snippet: <img srcset="/sites/default/files/styles/16_9_320x180/public/dam/lrdx2urjde/ieee-homepa…" sizes="100vw" width="1600" height="900" src="/sites/default/files/styles/16_9_768x432/public/dam/lrdx2urjde/ieee-homepa…" alt="An artistic rendering of binary code moving through an electric blue cable." loading="lazy">

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
value: No additional origins are good candidates for preconnecting

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.

URLTransfer SizeDuration
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd...34.2 KiB750 ms
s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js5.5 KiB1.6 s
app-ab24.marketo.com/js/forms2/js/forms2.min.js67.5 KiB2.3 s
cookie-consent.ieee.org/ieee-cookie-banner.css1008 B756 ms
up.pixel.ad/assets/up.js?um=13.1 KiB755 ms
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano.js49.1 KiB2.1 s
/css2?family=Open+Sans:ital,wdth,wght@0,75..100,300..800;...2.1 KiB759 ms
/sites/default/files/css/css_3DvgFGadp5NUrykuU7azDfJ8-UTu...49.8 KiB1.6 s
www.ieee.org/modules/contrib/google_tag/js/gtm.js?tdfs3g1.0 KiB
/sites/default/files/js/js_3kIRUGk5Tv1k0yGY6V0NMwK_2Dx0Or...844 B
www.ieee.org/modules/contrib/google_tag/js/gtag.js?tdfs3g1.0 KiB
/sites/default/files/css/css_6oBK-w_rALu9r1FiHEczqwSU3-96...2.9 KiB

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
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 KiB35.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 KiB24.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 KiB23.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 KiB8.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 KiB6.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.

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.

Estimated savings: 5.1 s
URLTime 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 613 ms
URLTime Spent
www.ieee.org/713 ms

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.

Estimated savings: 150 ms 43.5 KiB
URLTransfer SizeEst Savings
/sites/default/files/css/css_3DvgFGadp5NUrykuU7azDfJ8-UTu...49.2 KiB43.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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Estimated savings: 750 ms 1.0 MiB
URLTransfer SizeEst Savings
/sites/default/files/js/js_GaFm6NCGvHFQ3E7YTtKx1lvMqIIsdp...160.3 KiB113.7 KiB
www.googletagmanager.com/gtag/js?id=G-DGBMH9NVB4&cx=c&gtm=4e64f0173.0 KiB76.5 KiB
www.googletagmanager.com/gtag/js?id=G-TBNV764ZC7&cx=c&gtm=4e64f0175.6 KiB75.7 KiB
www.googletagmanager.com/gtag/js?id=G-W7T9YQJQXP&cx=c&gtm=4e64f0171.6 KiB73.8 KiB
www.googletagmanager.com/gtag/js?id=G-H0YHKP362D&cx=c&gtm=4e64f0169.6 KiB73.7 KiB
www.googletagmanager.com/gtag/js?id=G-DRSMCND71P&cx=c&gtm=4e64f0158.9 KiB70.4 KiB
www.googletagmanager.com/gtag/js?id=G-RN78LDXHRB&cx=c&gtm=4e64f0155.5 KiB68.8 KiB
www.googletagmanager.com/gtag/js?id=G-2ECHQV3WD3&cx=c&gtm=4e64f0156.5 KiB68.1 KiB
www.googletagmanager.com/gtag/js?id=G-HNLQ4ZWTQN&cx=c&gtm=4e64f0155.9 KiB67.5 KiB
www.googletagmanager.com/gtag/js?id=UA-23137171-17&cx=c&gtm=4e64f0115.5 KiB63.5 KiB
www.googletagmanager.com/gtm.js?id=GTM-MLL6HVG6130.9 KiB62.8 KiB
www.googletagmanager.com/gtag/destination?id=AW-852935669&cx=c&gtm=4e64f0143.3 KiB61.1 KiB
www.googletagmanager.com/gtag/js?id=DC-4490791&cx=c&gtm=4e64f0129.2 KiB56.8 KiB
www.googletagmanager.com/gtag/js?id=AW-1030676118&cx=c&gtm=4e64f0136.4 KiB55.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-P24WBM200.3 KiB48.1 KiB
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd...83.3 KiB23.9 KiB

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTotal CPU TimeScript EvaluationScript Parse
www.googletagmanager.com/gtm.js?id=GTM-P24WBM1.1 s912 ms150 ms
Unattributable875 ms16 ms0.0 ms
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano.js848 ms684 ms24 ms
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd...784 ms562 ms38 ms
www.ieee.org/763 ms47 ms11 ms
/sites/default/files/js/js_GaFm6NCGvHFQ3E7YTtKx1lvMqIIsdp...593 ms380 ms71 ms
www.googletagmanager.com/gtag/js?id=G-2ECHQV3WD3&cx=c&gtm=4e64f0525 ms310 ms162 ms
www.googletagmanager.com/gtag/js?id=G-RN78LDXHRB&cx=c&gtm=4e64f0484 ms271 ms61 ms
www.googletagmanager.com/gtag/js?id=G-TBNV764ZC7&cx=c&gtm=4e64f0402 ms329 ms71 ms
www.googletagmanager.com/gtm.js?id=GTM-MLL6HVG6363 ms304 ms55 ms
www.googletagmanager.com/gtag/js?id=G-HNLQ4ZWTQN&cx=c&gtm=4e64f0363 ms304 ms57 ms
www.googletagmanager.com/gtag/js?id=AW-1030676118&cx=c&gtm=4e64f0359 ms306 ms48 ms
www.googletagmanager.com/gtag/js?id=G-DGBMH9NVB4&cx=c&gtm=4e64f0355 ms283 ms70 ms
www.googletagmanager.com/gtag/js?id=G-DRSMCND71P&cx=c&gtm=4e64f0343 ms281 ms60 ms
www.googletagmanager.com/gtag/js?id=G-W7T9YQJQXP&cx=c&gtm=4e64f0342 ms269 ms71 ms
www.googletagmanager.com/gtag/js?id=G-H0YHKP362D&cx=c&gtm=4e64f0335 ms266 ms67 ms
www.googletagmanager.com/gtag/js?id=DC-4490791&cx=c&gtm=4e64f0324 ms273 ms48 ms
www.googletagmanager.com/gtag/destination?id=AW-852935669&cx=c&gtm=4e64f0306 ms249 ms54 ms
www.googletagmanager.com/gtag/js?id=UA-23137171-17&cx=c&gtm=4e64f0200 ms156 ms43 ms
/TSPD/08d3fc6170ab200031764f9a3cb1dfb2fa02ac1e6d6296f03cd...150 ms120 ms24 ms
www.google-analytics.com/analytics.js126 ms118 ms7.3 ms
/utag/travelers/thirdparty-us/prod/utag.3.js?utv=ut4.46.2...76 ms72 ms2.3 ms
/utag/travelers/thirdparty-us/prod/utag.4.js?utv=ut4.46.2...69 ms67 ms1.4 ms
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano-ui.js64 ms29 ms16 ms
tags.tiqcdn.com/utag/travelers/thirdparty-us/prod/utag.js60 ms54 ms4.4 ms
s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js60 ms58 ms1.1 ms

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 Evaluation6.8 s
Script Parsing & Compilation1.2 s
Other1.2 s
Style & Layout575 ms
Garbage Collection289 ms
Parse HTML & CSS190 ms
Rendering101 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 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 2.3 KiB
URLTransfer SizeEst Savings
s3.amazonaws.com/ieee-mkto-cross-domain/enterprise-page-code.js5.1 KiB2.3 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLTransfer Size
/seeds/31514831/assets/asset-view/2/0/7/0/20704fef-8c54-4...5.4 MiB
www.ieee.org/212.1 KiB
www.googletagmanager.com/gtm.js?id=GTM-P24WBM200.4 KiB
www.googletagmanager.com/gtag/js?id=G-TBNV764ZC7&cx=c&gtm=4e64f0175.6 KiB
www.googletagmanager.com/gtag/js?id=G-DGBMH9NVB4&cx=c&gtm=4e64f0173.1 KiB
www.googletagmanager.com/gtag/js?id=G-W7T9YQJQXP&cx=c&gtm=4e64f0171.6 KiB
www.googletagmanager.com/gtag/js?id=G-H0YHKP362D&cx=c&gtm=4e64f0169.6 KiB
/sites/default/files/js/js_GaFm6NCGvHFQ3E7YTtKx1lvMqIIsdp...160.8 KiB
www.googletagmanager.com/gtag/js?id=G-DRSMCND71P&cx=c&gtm=4e64f0159.0 KiB
www.googletagmanager.com/gtag/js?id=G-2ECHQV3WD3&cx=c&gtm=4e64f0156.5 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.
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.

●Layout shift culprits
●Optimize DOM size
●Font display
●Forced reflow
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●User Timing marks and measures 183 user timings
●Avoid long main-thread tasks 20 long tasks found
●Avoid non-composited animations 2 animated elements found
●Network Requests
●Network Round Trip Times 250 ms
●Server Backend Latencies 60 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid large layout shifts 1 layout shift found
○INP breakdown
97

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

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

Why this matters

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
○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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●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
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields 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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Image elements do not have `[alt]` attributes that are redundant text.
○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.
54

Best Practices

Trust and Safety

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Insecure URLRequest Resolution
burp/favicon.icoAutomatically upgraded to HTTPS

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 / WarningSource
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

Why this matters

Performance issues directly impact user engagement and conversion rates.

SourceDescription
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
127.0.0.1:8888/404
Failed to load resource: net::ERR_CONNECTION_REFUSED
127.0.0.1:8888/random_url
Failed to load resource: net::ERR_CONNECTION_REFUSED
127.0.0.1:8888/400_random_url_with_numbers_403
Failed to load resource: net::ERR_CONNECTION_REFUSED
127.0.0.1:8888/200
Failed to load resource: net::ERR_CONNECTION_REFUSED
127.0.0.1:8888/403
Failed to load resource: net::ERR_CONNECTION_REFUSED
127.0.0.1:8888/302
Failed to load resource: net::ERR_CONNECTION_REFUSED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
invalid/
Failed to load resource: net::ERR_FAILED
securesso.ieee.org/ieeevendorsso/rest/auth/validatePFToken?_=1776361720400
Failed to load resource: net::ERR_FAILED
burp/favicon.ico
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
www.ieee.org/favicon.ico
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.

Why this matters

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLMap URL
/sites/default/files/js/js_GaFm6NCGvHFQ3E7YTtKx1lvMqIIsdp...
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano.js/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/o...
cmp.osano.com/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/osano-ui.js/AzyzptTmRlqVd2LRf/ef7b712c-ff87-4229-b9ae-c1083228fb7f/o...
●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
●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
○Redirects HTTP traffic to HTTPS
○Mitigate clickjacking with XFO or CSP
92

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

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 isn’t blocked from indexing
●Document has a `<title>` element
●Page has successful HTTP status code
●Links have descriptive text
●Links are crawlable
●robots.txt is valid
●Image elements have `[alt]` attributes
●Document has a valid `hreflang`
○Document has a valid `rel=canonical`

Send Feedback