Skip to content
https://observer.com

Lighthouse Desktop

· 0 checks — Desktop 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.

89

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:56.648 source:map[column:8328 line:1 type:source-location url:https://observer.com/wp-content/plugins/xcurrent/assets/js/lazy-load.js?ver=6bd186b35f60946321703040eae7bccf 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:67.098 source:map[type:text value:[unattributed]]] map[reflowTime:56.648 source:map[column:4060 line:0 type:source-location url:https://observer.com/wp-content/plugins/xcurrent/assets/js/lazy-load.js?ver=6bd186b35f60946321703040eae7bccf urlProvider:network]] map[reflowTime:0.44 source:map[column:3330 line:0 type:source-location url:https://www.npttech.com/advertising.js urlProvider:network]] map[reflowTime:32.287 source:map[column:3408 line:0 type:source-location url:https://www.npttech.com/advertising.js urlProvider:network]] map[reflowTime:0.361 source:map[column:73123 line:0 type:source-location url:https://truculentrate.com/scripts/3f92345fab9c/22bdf0221b6555de6cdadcba urlProvider:network]] map[reflowTime:0.35 source:map[column:72793 line:0 type:source-location url:https://truculentrate.com/scripts/3f92345fab9c/22bdf0221b6555de6cdadcba urlProvider:network]]]

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

lhId: page-0-IMG
nodeLabel: div.featured-content__main > article.post-card > a.post-card__image > img
path: 1,HTML,1,BODY,3,DIV,1,DIV,2,DIV,0,MAIN,0,ARTICLE,0,DIV,0,SECTION,0,DIV,0,ARTICLE,0,A,0,IMG
selector: div.featured-content__main > article.post-card > a.post-card__image > img
snippet: <img src="https://observer.com/wp-content/uploads/sites/2/2026/04/Photo-16-10-2023-1…" alt="" loading="eager">

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

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
s.ntv.io/serve/load.js?ver=1.0.03600.0 s251.1 KiB
sandbox.tinypass.com/api/tinypass.min.js14400.0 s132.6 KiB
connect.facebook.net/en_US/fbevents.js1200.0 s96.6 KiB
c.amazon-adsystem.com/aax2/apstag.js3600.0 s90.9 KiB
/observermedia-OPVkdFmD2x/observer.com/prebid-wrapper.js3600.0 s74.7 KiB
ak.sail-horizon.com/spm/spm.v1.min.js?ver=5.5.1600.0 s48.1 KiB
/signals/config/618909876214345?v=2.9.303&r=stable&domain...1200.0 s44.4 KiB
cdn.cookielaw.org/scripttemplates/6.9.0/otBannerSdk.js86400.0 s74.3 KiB
cdn.id5-sync.com/api/1.0/id5-api.js3600.0 s34.4 KiB
secure.cdn.fastclick.net/js/pubcid/latest/pubcid.min.js900.0 s21.7 KiB
/signals/config/832096553515722?v=2.9.303&r=stable&domain...1200.0 s18.0 KiB
www.google-analytics.com/analytics.js7200.0 s20.9 KiB
/observermedia-OPVkdFmD2x/observer.com/prebid-load.js3600.0 s16.5 KiB
htlbid.com/v3/observer.com/htlbid.js?ver=3.0600.0 s12.3 KiB
raven-static.aditude.io/prod/1.19.14-y0ptsc/raven.js604800.0 s107.1 KiB
rampjs-cdn.system1.com/ramp.js3600.0 s11.8 KiB
static.hotjar.com/c/hotjar-3537567.js?sv=760.0 s6.2 KiB
tags.crwdcntrl.net/lt/c/16576/sync.min.js86400.0 s13.1 KiB
/scripttemplates/otSDKStub.js?did=6a95224d-e53b-4c23-b2a6...86400.0 s9.1 KiB
cdn.cookielaw.org/scripttemplates/otSDKStub.js86400.0 s8.6 KiB
sb.scorecardresearch.com/internal-cs/default/beacon.js86400.0 s6.7 KiB
sb.scorecardresearch.com/beacon.js86400.0 s6.7 KiB
raven-edge.aditude.io/raven/observermedia-main-2zyPw/library.js300.0 s2.6 KiB
/components/htl-injector-component.6f9fd855080891057769.js86400.0 s5.2 KiB
www.npttech.com/advertising.js28800.0 s3.0 KiB
/components/creative-timed-refresh-component.a1a922b43837...86400.0 s4.1 KiB
config.aps.amazon-adsystem.com/configs/4e8fb3b2-1c6c-42d6-890c-e5a6718315a33600.0 s1.8 KiB
sandbox.tinypass.com/xbuilder/experience/load?aid=CMrLcDjZsu1800.0 s1.5 KiB
/components/first-party-data-component.9031b6342187473708...86400.0 s2.9 KiB
/components/schain-config-component.ed1cd260619f0e580cd3.js86400.0 s2.4 KiB
/components/throttle-refresh-component.de8e70e8b17a42bbf0...86400.0 s1.6 KiB
/components/activity-refresh-component.059097ebda70e7a178...86400.0 s1.6 KiB
www.google-analytics.com/plugins/ua/linkid.js3600.0 s722 B
/prod/1.19.14-y0ptsc/prebid-analytics.980e6134af0dbb700d9...604800.0 s5.5 KiB
/components/refresh-all-ads-component.db7de998acab3aec35b...86400.0 s1.4 KiB
rules.quantcount.com/rules-p-UtaLhd9K6h6Mf.js3600.0 s644 B
/components/htl-traffic-shaping-component.05bf9326dea218a...86400.0 s1.2 KiB
/components/taboola-auto-tagId-component.d35311409295ad80...86400.0 s1.1 KiB
www.gstatic.com/recaptcha/api2/logo_48.png604800.0 s2.3 KiB
/tr/?id=618909876214345&ev=PageView&dl=https%3A%2F%2Fobse...0.0 ms16 B
/tr/?id=832096553515722&ev=PageView&dl=https%3A%2F%2Fobse...0.0 ms16 B

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLResource SizeEst Savings
A collage of three men and a woman div.channel-content__secondary > article.post-card > a.post-card__image > img.attachment-medium
/wp-content/uploads/sites/2/2026/04/Untitled_57564c.png?r...70.1 KiB68.0 KiB
Two men walking in a park div.channel-content__main > article.post-card > a.post-card__image > img.attachment-medium
/wp-content/uploads/sites/2/2026/04/Apple-John-Ternus-Tim...15.5 KiB6.4 KiB

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.

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

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: 873 ms
URLTime Spent
observer.com/973 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

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.

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

CategoryTime Spent
Script Evaluation1.7 s
Style & Layout300 ms
Other292 ms
Script Parsing & Compilation253 ms
Parse HTML & CSS56 ms
Rendering52 ms
Garbage Collection32 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

●Max Potential First Input Delay 80 ms
●Layout shift culprits
●Optimize DOM size
●LCP breakdown
●Modern HTTP
●Optimize viewport for mobile
●Minify CSS
●Minify JavaScript
●User Timing marks and measures 13 user timings
●Avoid long main-thread tasks 9 long tasks found
●Avoid non-composited animations 1 animated element found
●Image elements have explicit `width` and `height`
●Page didn't prevent back/forward cache restoration
●Network Requests
●Network Round Trip Times 100 ms
●Server Backend Latencies 1,050 ms
●Tasks
●Diagnostics
●Metrics
●Screenshot Thumbnails
●Final Screenshot
●Script Treemap Data
●Resources Summary
●Avoid multiple page redirects
●Avoid large layout shifts 8 layout shifts found
○INP breakdown
88

Accessibility

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

ARIA

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

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
By clicking “Accept All Cookies”, you agree to the storing of cookies on your d… body.home > div#onetrust-consent-sdk > div#onetrust-banner-sdk

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

Contrast

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Powered by WordPress VIP div.inner-container > div.bottom > div.right > div.vip-powered
WordPress VIP div.bottom > div.right > div.vip-powered > a.powered-by-wpcom
Learn more div.fc-dialog-content > div.fc-dialog-scrollable-content > button.fc-faq-header > span.fc-faq-label
List of partners. div.fc-dialog-scrollable-content > div.fc-footer > p > a.fc-vendors-list-dialog
Manage options div.fc-dialog > div.fc-footer-buttons-container > button.fc-button > p.fc-manage-options-third-button-label

These are opportunities to improve the legibility of your content.

Best practices

Users do not expect a page to refresh automatically, and doing so will move focus back to the top of the page. This may create a frustrating or confusing experience. Learn more about the refresh meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
body.home > meta body.home > meta

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●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
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
○`[role]`s are contained by their required parent element
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○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.
○Image elements have `[alt]` attributes
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○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.
77

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

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
%cCW display: inline-block; color: #fff; font-size: 9px; background: #61B321; padding: 1px 4px; border-radius: 0; margin-right: 1px; Missing a base prebid mapping for base ".htlad-observer_1x1_2"
Failed to load resource: the server responded with a status of 502 ()
observer.com/ line 1740, col 0
ReferenceError: wp is not defined at https://observer.com/:1741:1
●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 issues in the `Issues` panel in Chrome Devtools
●Ensure CSP is effective against XSS attacks
●Ensure proper origin isolation with COOP
●Mitigate clickjacking with XFO or CSP
●Mitigate DOM-based XSS with Trusted Types
●Detected JavaScript libraries
●Page has valid source maps
○Redirects HTTP traffic to HTTPS
○Use a strong HSTS policy
83

SEO

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

Content Best Practices

Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Link destinationLink Text
observer.com/latest/MORE

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

Crawling and Indexing

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Uncrawlable Link
How Do I Whitelist Observer? div#adb-notification > div.message-container > div.message > a#adb-whitelist
Then Reload the Page div#adb-notification > div.message-container > div.message > a#adb-reload

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

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

Send Feedback