Skip to content
Audit Complete

Results for https://robbreport.com

Visit site
Corporate / Enterprise · estimated Tracking: leads
Spain Spain · Madrid Completed: Apr 22, 2026 22:43 UTC
Download JSON Download Markdown Report

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

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

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

Room to improve — your 4.9s load time is above Google's 2.5s 'Good' threshold.

Good foundation, but a few gaps could be exploited.

Several issues make your site difficult for assistive technology users.

Well-optimized for search — your content is discoverable.

Solid infrastructure — fast server responses across the board.

Mostly compliant — a few items need attention.

Good content signals with minor gaps.

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

How is this calculated?

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

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

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

How the composite score is calculated

How you compare

WordPress · 712 peers
You 74
·
Avg 74
At average
0 50 100
Better than 42% of WordPress sites See full WordPress benchmark →
Admiral · 92 peers
You 74
·
Avg 72
At average
0 50 100
Better than 61% of Admiral sites See full Admiral benchmark →

Top Priorities (5)

1

Page weighs 10.6 MB (4.6 MB transferred)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
2

1 control(s) without accessible label

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

Accessibility › Form Accessibility
3

6 button(s) with no accessible text

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

Accessibility › Link & Button Quality
4

144 third-party resources (84% of weight)

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Inventory
5

212 HTTP requests — consider bundling or reducing

Performance issues directly impact user engagement and conversion rates.

Performance › Page Weight Budget
View fix priority matrix

Fix Priority Matrix

5 findings

Quick Wins

0

High impact, low effort — start here.

Nothing in this quadrant — good news.

Strategic

5

High impact, requires investment.

Easy Improvements

0

Small gains, minimal effort.

Nothing in this quadrant — good news.

Deprioritize

0

Low impact, high effort — do last.

Nothing in this quadrant — good news.

← Low effort High effort →
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Frobbreport.com)](https://beavercheck.com/results/60933e0a-ab05-454a-abe5-9658d70e202b)
<a href="https://beavercheck.com/results/60933e0a-ab05-454a-abe5-9658d70e202b"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Frobbreport.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Frobbreport.com

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. Your LCP of 4.9s exceeds Google's 2.5s 'Good' threshold and the 3 performance issues below directly contribute 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 conversion rate.

Your LCP is 4.9s — fixing the 3 performance criticals could bring it under Google's 2.5s 'Good' threshold.
2 accessibility issues exclude users who rely on assistive technology.

Conversion Barriers

4 critical 5 warning

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

Speed (2)

Page takes 4.9s to load

+12% bounce

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

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

Page feels frozen for 1.2s

+5% bounce

Clicks on the primary CTA are ignored while JavaScript runs

Fix: Break up long tasks; defer non-critical JavaScript to post-hydration

Trust (3)

Mixed content on HTTPS page

+8% bounce

Browsers block insecure subresources — broken images, missing scripts, warning badge

Fix: Change http:// URLs inside the page to https:// (or protocol-relative)

No HSTS header

+1% bounce

Returning visitors are briefly exposed to downgrade attacks on first request

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

No Content-Security-Policy header

+1% bounce

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

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

Usability (2)

1 form field(s) without a label

+2% bounce

Screen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes

Fix: Associate every input with a visible <label for="…">; add autocomplete attributes

Viewport disables user zoom

+2% bounce

Visitors with low vision can't read the page — and some jurisdictions treat this as a legal risk

Fix: Remove user-scalable=no; drop maximum-scale if it's below 2

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

30 broken link(s) on the page

+5% 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

$900 investment → $3,514/month returns + USD 157,500 risk avoided

Payback period: < 1 month First-year ROI: +4586%

Investment

$900

9h · 5 findings

Monthly returns

$3,514 /mo

~$42,170 / year

  • Conversions recovered $3,513
  • Bandwidth savings $1.16

Regulatory risk avoided

USD 157,500

if kept compliant

  • ADA Title III USD 150,000
  • CCPA/CPRA USD 7,500

Payback period

0 12mo 24mo

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

$900

9.0 developer hours at $100/hr

Based on United States rates ($100/hr)

Cost by category

Cost by effort level

Adjust assumptions
$ /hr

Rates reflect fully-loaded developer cost including overhead

How developer rates are sourced

What Inaction Is Costing You

$13,126 / month at risk

~$157,514 / year if left unfixed

Compliance Risk

$157,500

ADA Title IIICCPA/CPRA
  • No privacy policy link detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • 1 advertising/retargeting trackers detected
    CCPA/CPRA: USD 2,500 – USD 7,500
  • Trackers detected but no cookie policy found
    CCPA/CPRA: USD 2,500 – USD 7,500

+6 more

Bandwidth Waste

$1.16 /mo

14522.7 MB/mo × 0.080 USD/GB

  • Optimize transfer: save ~1.5 MB per page load
    Saves $1.16/mo

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

Compliance methodology · SEO assumptions · Bandwidth model

Your performance is already good — improvements may show diminishing returns

Unique monthly visitors from your analytics

Purchases, signups, or key actions

Optional — for revenue estimation

additional conversions/month

more engaged visitors from reduced bounce

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

Fix 3 critical issues to capture this value

How this is calculated

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

Your site's LCP: → estimated after fixes.

These are estimates based on industry research — actual results vary

Bounce-rate model & assumptions

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

Was this report useful?

Thanks for your feedback!

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

Checking for existing audit...

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

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

Core Web Vitals

Key metrics that affect user experience.

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

2.56 s

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

4.91 s

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

1.18 s

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

0.003

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

5.74 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.75 s

Detailed Report

Audit breakdown by category with detailed findings.

50

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.

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.

URLEst Savings
/af/8829c1/00000000000000003b9ae8db/27/l?primer=7cdcb44be...120 ms
/af/d28e99/00000000000000003b9ae8ed/27/l?primer=f592e0a4b...120 ms
/af/2566bd/00000000000000003b9ae903/27/l?primer=7cdcb44be...120 ms
/af/a079a0/00000000000000007736b5bb/30/l?primer=f592e0a4b...115 ms
/af/888209/00000000000000007735c628/30/l?primer=7cdcb44be...115 ms
/af/6dbb57/00000000000000007736b5aa/30/l?primer=f592e0a4b...110 ms
/af/7a3e92/00000000000000007736b5ab/30/l?primer=f592e0a4b...110 ms
/af/5441ea/00000000000000007736b5b2/30/l?primer=f592e0a4b...110 ms
/af/5d2b8a/00000000000000007736b5b0/30/l?primer=f592e0a4b...110 ms
/af/e7b122/00000000000000007736b59f/30/l?primer=f592e0a4b...105 ms
/af/46d471/00000000000000007736b5b3/30/l?primer=f592e0a4b...105 ms
/af/fec50e/00000000000000007736b5b5/30/l?primer=f592e0a4b...100 ms
/af/e1ee59/00000000000000007736b5a6/30/l?primer=f592e0a4b...100 ms
/af/5c348d/00000000000000007736b5af/30/l?primer=f592e0a4b...95 ms
/af/443a3e/0000000000000000774a6731/30/l?primer=7cdcb44be...90 ms
/af/478e11/00000000000000003b9ae169/27/l?primer=7cdcb44be...90 ms
/af/88cd08/0000000000000000774a6728/30/l?primer=7cdcb44be...85 ms
/af/5a6493/0000000000000000774a6724/30/l?primer=7cdcb44be...85 ms
/af/9d651e/0000000000000000774a672f/30/l?primer=7cdcb44be...85 ms
/af/2d8465/0000000000000000774a6723/30/l?primer=7cdcb44be...80 ms
/af/466de5/0000000000000000774a6725/30/l?primer=7cdcb44be...80 ms
/af/8e0c3d/00000000000000007736b5b7/30/l?primer=7cdcb44be...75 ms
/af/4e9301/00000000000000007736b5ac/30/l?primer=7cdcb44be...75 ms
/af/2f2de2/0000000000000000774a672b/30/l?primer=7cdcb44be...75 ms
/af/5ff898/00000000000000007736b5b8/30/l?primer=7cdcb44be...70 ms
/af/569714/00000000000000007736b5a9/30/l?primer=7cdcb44be...70 ms
/af/69429d/00000000000000007736b5ad/30/l?primer=7cdcb44be...70 ms
/af/1aadf0/00000000000000007736b5c0/30/l?primer=7cdcb44be...70 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff265 ms
/af/1f3d78/00000000000000007736b59d/30/l?primer=7cdcb44be...65 ms
/af/028365/00000000000000007736b59e/30/l?primer=7cdcb44be...65 ms
/af/a3b977/00000000000000007736b5a4/30/l?primer=7cdcb44be...65 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh50XSwiPGQ3q5d0.woff260 ms
/af/d521f7/00000000000000003b9ae147/27/l?primer=7cdcb44be...60 ms
/af/aaa21d/00000000000000007736b599/30/l?primer=7cdcb44be...60 ms
/af/112698/00000000000000007736b5b4/30/l?primer=7cdcb44be...60 ms
/af/69cf60/00000000000000007736b5bf/30/l?primer=7cdcb44be...60 ms
/af/e11748/00000000000000007736b5a5/30/l?primer=7cdcb44be...60 ms
/af/e95231/00000000000000007736b5b9/30/l?primer=7cdcb44be...60 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh7USSwiPGQ3q5d0.woff255 ms
/af/14d146/00000000000000007736b59a/30/l?primer=7cdcb44be...55 ms
/af/3b579a/00000000000000007736b5b1/30/l?primer=7cdcb44be...55 ms
/af/6d496a/00000000000000007736b5a7/30/l?primer=7cdcb44be...55 ms
/af/57992f/00000000000000007736b5be/30/l?primer=7cdcb44be...55 ms
/af/5e355d/00000000000000007736b5bc/30/l?primer=7cdcb44be...55 ms
/af/13e7c0/00000000000000003b9ae90a/27/l?primer=7cdcb44be...50 ms
/af/d90646/00000000000000007736b5ba/30/l?primer=7cdcb44be...50 ms
/af/e13dab/00000000000000007736b5a1/30/l?primer=7cdcb44be...50 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff245 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff245 ms
/af/234bee/00000000000000003b9ae8fc/27/l?primer=7cdcb44be...45 ms
/af/fdeb24/00000000000000003b9ae901/27/l?primer=7cdcb44be...45 ms
/af/a193b7/00000000000000003b9ae908/27/l?primer=7cdcb44be...45 ms
/af/c3156c/00000000000000003b9ae8de/27/l?primer=7cdcb44be...40 ms
/af/407987/00000000000000003b9ae8e9/27/l?primer=f592e0a4b...40 ms
/af/5d1a4a/00000000000000003b9ae8ea/27/l?primer=f592e0a4b...40 ms
/af/fa0ce1/00000000000000003b9ae8ef/27/l?primer=f592e0a4b...40 ms
/af/9c4ca1/00000000000000003b9ae8fa/27/l?primer=7cdcb44be...35 ms
fonts.gstatic.com/s/lato/v25/S6uyw4BMUTPHjx4wXiWtFCc.woff235 ms
/af/d58aa1/00000000000000003b9ae8e0/27/l?primer=7cdcb44be...35 ms
/af/ea98f6/00000000000000003b9ae8e5/27/l?primer=7cdcb44be...35 ms
/af/372551/00000000000000003b9ae8e7/27/l?primer=7cdcb44be...35 ms
/af/316130/00000000000000003b9ae8dc/27/l?primer=7cdcb44be...30 ms
/af/1100b4/00000000000000003b9ae8df/27/l?primer=7cdcb44be...30 ms
/af/02b3bb/00000000000000003b9ae8e1/27/l?primer=7cdcb44be...30 ms
/af/fa8648/00000000000000003b9ae8eb/27/l?primer=f592e0a4b...25 ms
/af/322f06/00000000000000003b9ae8f3/27/l?primer=7cdcb44be...25 ms
/af/26c587/00000000000000003b9ae8f5/27/l?primer=7cdcb44be...25 ms
/af/a1a121/00000000000000003b9ae8ec/27/l?primer=f592e0a4b...20 ms
/af/e78554/00000000000000003b9ae8dd/27/l?primer=7cdcb44be...20 ms
/af/4b637b/00000000000000003b9ae8ee/27/l?primer=f592e0a4b...15 ms

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:5.703 source:map[column:2103 line:1 type:source-location url: 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.384 source:map[column:49615 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:64.832 source:map[column:50335 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.282 source:map[column:50393 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.158 source:map[column:50457 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.326 source:map[column:51395 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.049 source:map[column:49637 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:5.427 source:map[column:826 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.082 source:map[column:1033 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.104 source:map[column:1071 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.084 source:map[column:70434 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:15.683 source:map[type:text value:[unattributed]]] map[reflowTime:0.979 source:map[column:327363 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:5.703 source:map[column:73056 line:0 type:source-location url:https://fillthemap.com/chunks/k8dp76/qwke7z.vendor.js urlProvider:network]] map[reflowTime:0.277 source:map[column:66956 line:1 type:source-location url:https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js urlProvider:network]] map[reflowTime:0.226 source:map[column:223131 line:1 type:source-location url:https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.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.

URLResource SizeEst Savings
Four Roses Single Barrels article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
/wp-content/uploads/2026/04/Four_Roses_Single_Barrels_202...146.8 KiB137.4 KiB
les colombieres menton article.editor-picks__secondary-pick > div.featured-image > a > img.attachment-featured-image-320x180
robbreport.com/wp-content/uploads/2026/04/lescolombieres.jpg?resize=681,38361.3 KiB49.5 KiB
150 Littlefield Shirley Temple Wedding House Monterey article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
/wp-content/uploads/2026/04/ShirleyTempleWedding-House_CA...31.5 KiB22.1 KiB
Bulgari Octo Finissimo, Jaeger-LeCoultre Master Control Perpetual Calendar, Par… article.editor-picks__secondary-pick > div.featured-image > a > img.attachment-featured-image-320x180
/wp-content/uploads/2026/04/RR_20260421_Watches_Wonders_E...27.5 KiB22.0 KiB
magazine cover div.header-subscribe__container-inner > div.header-get__magazine-container > div.gtm-sub-cover > img.gtm-cover
/wp-content/uploads/2026/04/Untitled-design-6.png?w=150&h...25.5 KiB21.1 KiB
X Square Robot new Wall-B robot arranges flowers article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
robbreport.com/wp-content/uploads/2026/04/x-square-robot-wall-b1.jpg?w=48025.9 KiB16.5 KiB
amsterdam netherlands most expensive home listing article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
robbreport.com/wp-content/uploads/2026/04/amsterdam-most-exp.jpg?w=48022.4 KiB10.6 KiB
The factory-restored 1972 Lamborghini Miura SV article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
/wp-content/uploads/2026/04/restored-1972-lamborghini-miu...21.4 KiB9.7 KiB
Timothée Chalamet; Urban Jürgensen UJ2 article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
/wp-content/uploads/2026/04/Timothee-Chalamet-Urban-Jurge...14.1 KiB7.8 KiB
TAG Heuer Formula 1 Solargraph article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
/wp-content/uploads/2026/04/tag-heuer-formula-1-solargrap...11.9 KiB6.6 KiB
The JAS Motorsport Tensei article.featured-category__story > div.featured-image > a > img.attachment-featured-image-480x270
robbreport.com/wp-content/uploads/2026/04/jas-motorsport-tensei-01.jpg?w=48010.2 KiB4.5 KiB

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.

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
cdn.tinypass.com/api/tinypass.min.js14400.0 s132.6 KiB
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js14400.0 s132.1 KiB
connect.facebook.net/en_US/bundle/sdk.js/1200.0 s78.5 KiB
ads.blogherads.com/static/chunks/3622.7d0e84ccad5146cd86e6.js14400.0 s50.2 KiB
ads.blogherads.com/static/chunks/831.b113b40433677910de75.js14400.0 s43.4 KiB
ads.blogherads.com/static/chunks/2030.b94af747cd5b3350d333.js14400.0 s19.8 KiB
use.typekit.net/oxq7mos.js600.0 s8.9 KiB
ads.blogherads.com/static/chunks/982.31e834f3c5c91bf8b371.js14400.0 s11.4 KiB
ads.blogherads.com/static/chunks/4857.910c4b46763f23e61854.js14400.0 s7.9 KiB
ads.blogherads.com/sk/00/000/00000/27336/header.js14400.0 s7.3 KiB
connect.facebook.net/en_US/sdk.js1200.0 s5.0 KiB
ads.blogherads.com/static/chunks/6559.074815d12fef9b41149e.js14400.0 s6.3 KiB
ads.blogherads.com/static/chunks/6317.7fde3be0f22be218a9d5.js14400.0 s4.8 KiB
ads.blogherads.com/static/blogherads.js14400.0 s4.4 KiB
cdn.keywee.co/dist/analytics-1.5.12.min.js259200.0 s7.9 KiB
rules.quantcount.com/rules-p-31f3D02tYU8zY.js3600.0 s1.7 KiB
d1mkq4fbm7j30i.cloudfront.net/21/oHS-21.js0.0 ms793 B
cmm.keywee.co/1146/main.min.js0.0 ms532 B
static.doubleclick.net/instream/ad_status.js900.0 s494 B
s3-us-west-2.amazonaws.com/jsstore/a/QKEH0ZG/ge.js0.0 ms405 B
cmm.keywee.co/1146/dist/aHR0cHM6Ly9yb2JicmVwb3J0LmNvbS8=.min.js0.0 ms396 B
iabusprivacy.pmc.com/geo-info.js0.0 ms265 B
ad-delivery.net/px.gif?ch=286400.0 s611 B
ad-delivery.net/px.gif?ch=186400.0 s109 B
/p.gif?s=1&k=oxq7mos&ht=tk&h=robbreport.com&f=31372.31373...604800.0 s205 B

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

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: 793 ms
URLTime Spent
robbreport.com/893 ms

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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 Evaluation2.4 s
Other1.0 s
Style & Layout855 ms
Script Parsing & Compilation433 ms
Rendering166 ms
Parse HTML & CSS108 ms
Garbage Collection20 ms

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

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

Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 17 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 170 ms
Server Backend Latencies 130 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
84

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.

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
Wednesday, April 22, 2026 nav.header-nav > div.header__subscribe-mobile > h3.header__subscribe--mobile-time > span
SHOP NOW div.gtm-sub-container > div.gtm-content > div > a.button
SUBSCRIBE div.header-get__magazine-container > div.gtm-content > div > a.button

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.sectioner > div.footer-rr1_container > div.footer-rr1_video > iframe section.sectioner > div.footer-rr1_container > div.footer-rr1_video > 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.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Wednesday, April 22, 2026 header > nav.header-nav > div.header__subscribe-mobile > h3.header__subscribe--mobile-time

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > 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
Image elements have `[alt]` attributes
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 have a discernible name
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`[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
`<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
Form elements have associated labels
Links are distinguishable without relying on color.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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
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.
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
Topics

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
%cP%cM%cC Atlas MG padding: 2px 1px 2px 10px; border-radius: 7px 0 0 7px; background-color: black; color: white; padding: 2px 1px; background-color: black; color: #ed1c24; padding: 2px 10px 2px 1px; border-radius: 0 7px 7px 0; background-color: black; color: white; Error: Time to wait for consent has expired. at s (https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js:2:106729) at Y (<anonymous>:1:2216)
ReferenceError: WebFont is not defined at Object.load (https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/assets/build/js/common.js?ver=1765796790:2:45831) at https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/assets/build/js/common.js?ver=1765796790:2:45754 at Y (<anonymous>:1:2216)
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
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
100

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.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

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

Core Web Vitals

Key metrics that affect user experience. — Desktop

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

649 ms

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

1.23 s

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

54 ms

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

0.002

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

1.82 s

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

3.11 s

Detailed Report

Audit breakdown by category with detailed findings.

94

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.

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.

URLEst Savings
/af/5441ea/00000000000000007736b5b2/30/l?primer=f592e0a4b...115 ms
/af/5d2b8a/00000000000000007736b5b0/30/l?primer=f592e0a4b...115 ms
/af/888209/00000000000000007735c628/30/l?primer=7cdcb44be...115 ms
/af/6dbb57/00000000000000007736b5aa/30/l?primer=f592e0a4b...110 ms
/af/7a3e92/00000000000000007736b5ab/30/l?primer=f592e0a4b...110 ms
/af/e7b122/00000000000000007736b59f/30/l?primer=f592e0a4b...105 ms
/af/46d471/00000000000000007736b5b3/30/l?primer=f592e0a4b...105 ms
/af/fec50e/00000000000000007736b5b5/30/l?primer=f592e0a4b...100 ms
/af/e1ee59/00000000000000007736b5a6/30/l?primer=f592e0a4b...100 ms
/af/a079a0/00000000000000007736b5bb/30/l?primer=f592e0a4b...100 ms
/af/69429d/00000000000000007736b5ad/30/l?primer=7cdcb44be...95 ms
/af/5c348d/00000000000000007736b5af/30/l?primer=f592e0a4b...95 ms
/af/9d651e/0000000000000000774a672f/30/l?primer=7cdcb44be...90 ms
/af/478e11/00000000000000003b9ae169/27/l?primer=7cdcb44be...90 ms
/af/88cd08/0000000000000000774a6728/30/l?primer=7cdcb44be...85 ms
/af/5a6493/0000000000000000774a6724/30/l?primer=7cdcb44be...85 ms
/af/028365/00000000000000007736b59e/30/l?primer=7cdcb44be...80 ms
/af/a3b977/00000000000000007736b5a4/30/l?primer=7cdcb44be...80 ms
/af/569714/00000000000000007736b5a9/30/l?primer=7cdcb44be...80 ms
/af/443a3e/0000000000000000774a6731/30/l?primer=7cdcb44be...80 ms
/af/2d8465/0000000000000000774a6723/30/l?primer=7cdcb44be...80 ms
/af/466de5/0000000000000000774a6725/30/l?primer=7cdcb44be...80 ms
/af/e95231/00000000000000007736b5b9/30/l?primer=7cdcb44be...75 ms
/af/5e355d/00000000000000007736b5bc/30/l?primer=7cdcb44be...75 ms
/af/5ff898/00000000000000007736b5b8/30/l?primer=7cdcb44be...75 ms
/af/1aadf0/00000000000000007736b5c0/30/l?primer=7cdcb44be...75 ms
/af/8e0c3d/00000000000000007736b5b7/30/l?primer=7cdcb44be...75 ms
/af/4e9301/00000000000000007736b5ac/30/l?primer=7cdcb44be...75 ms
/af/2f2de2/0000000000000000774a672b/30/l?primer=7cdcb44be...75 ms
/af/69cf60/00000000000000007736b5bf/30/l?primer=7cdcb44be...70 ms
/af/57992f/00000000000000007736b5be/30/l?primer=7cdcb44be...70 ms
/af/1f3d78/00000000000000007736b59d/30/l?primer=7cdcb44be...70 ms
/af/e11748/00000000000000007736b5a5/30/l?primer=7cdcb44be...70 ms
/af/2566bd/00000000000000003b9ae903/27/l?primer=7cdcb44be...65 ms
/af/112698/00000000000000007736b5b4/30/l?primer=7cdcb44be...65 ms
/af/6d496a/00000000000000007736b5a7/30/l?primer=7cdcb44be...60 ms
/af/d521f7/00000000000000003b9ae147/27/l?primer=7cdcb44be...60 ms
/af/aaa21d/00000000000000007736b599/30/l?primer=7cdcb44be...60 ms
/af/e13dab/00000000000000007736b5a1/30/l?primer=7cdcb44be...55 ms
/af/14d146/00000000000000007736b59a/30/l?primer=7cdcb44be...55 ms
/af/3b579a/00000000000000007736b5b1/30/l?primer=7cdcb44be...55 ms
/af/13e7c0/00000000000000003b9ae90a/27/l?primer=7cdcb44be...50 ms
/af/d90646/00000000000000007736b5ba/30/l?primer=7cdcb44be...50 ms
fonts.gstatic.com/s/roboto/v48/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff245 ms
fonts.gstatic.com/s/roboto/v51/KFO7CnqEu92Fr1ME7kSn66aGLdTylUAMa3yUBHMdazQ.woff245 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh6UVSwiPGQ3q5d0.woff245 ms
/af/8829c1/00000000000000003b9ae8db/27/l?primer=7cdcb44be...45 ms
/af/26c587/00000000000000003b9ae8f5/27/l?primer=7cdcb44be...45 ms
/af/fdeb24/00000000000000003b9ae901/27/l?primer=7cdcb44be...45 ms
/af/a193b7/00000000000000003b9ae908/27/l?primer=7cdcb44be...45 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh7USSwiPGQ3q5d0.woff240 ms
fonts.gstatic.com/s/lato/v25/S6u9w4BMUTPHh50XSwiPGQ3q5d0.woff240 ms
/af/5d1a4a/00000000000000003b9ae8ea/27/l?primer=f592e0a4b...40 ms
/af/d28e99/00000000000000003b9ae8ed/27/l?primer=f592e0a4b...40 ms
/af/fa0ce1/00000000000000003b9ae8ef/27/l?primer=f592e0a4b...40 ms
/af/322f06/00000000000000003b9ae8f3/27/l?primer=7cdcb44be...40 ms
/af/ea98f6/00000000000000003b9ae8e5/27/l?primer=7cdcb44be...35 ms
/af/372551/00000000000000003b9ae8e7/27/l?primer=7cdcb44be...35 ms
/af/407987/00000000000000003b9ae8e9/27/l?primer=f592e0a4b...35 ms
fonts.gstatic.com/s/lato/v25/S6uyw4BMUTPHjx4wXiWtFCc.woff230 ms
/af/1100b4/00000000000000003b9ae8df/27/l?primer=7cdcb44be...30 ms
/af/d58aa1/00000000000000003b9ae8e0/27/l?primer=7cdcb44be...30 ms
/af/02b3bb/00000000000000003b9ae8e1/27/l?primer=7cdcb44be...30 ms
/af/c3156c/00000000000000003b9ae8de/27/l?primer=7cdcb44be...25 ms
/af/4b637b/00000000000000003b9ae8ee/27/l?primer=f592e0a4b...20 ms
/af/a1a121/00000000000000003b9ae8ec/27/l?primer=f592e0a4b...15 ms
/af/9c4ca1/00000000000000003b9ae8fa/27/l?primer=7cdcb44be...15 ms
/af/fa8648/00000000000000003b9ae8eb/27/l?primer=f592e0a4b...10 ms
/af/234bee/00000000000000003b9ae8fc/27/l?primer=7cdcb44be...10 ms
/af/e78554/00000000000000003b9ae8dd/27/l?primer=7cdcb44be...10 ms
/af/316130/00000000000000003b9ae8dc/27/l?primer=7cdcb44be...5.0 ms

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:4.355 source:map[column:1140 line:1 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/home.bundle.min.js?ver=2024.5 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:51.499 source:map[column:49615 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:81.761 source:map[column:50335 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.269 source:map[column:50393 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.188 source:map[column:50457 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:29.541 source:map[type:text value:[unattributed]]] map[reflowTime:1.111 source:map[column:327363 line:0 type:source-location url:https://cdn.tinypass.com/api/tinypass.min.js urlProvider:network]] map[reflowTime:0.233 source:map[column:77191 line:1 type:source-location url:https://html-load.com/loader.min.js urlProvider:network]] map[reflowTime:0.22 source:map[column:51535 line:1 type:source-location url:https://html-load.com/loader.min.js urlProvider:network]] map[reflowTime:0.449 source:map[column:66956 line:1 type:source-location url:https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js urlProvider:network]] map[reflowTime:0.171 source:map[column:222849 line:1 type:source-location url:https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js urlProvider:network]] map[reflowTime:0.379 source:map[column:51395 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:0.037 source:map[column:49637 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 urlProvider:network]] map[reflowTime:4.103 source:map[column:826 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.075 source:map[column:1033 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.099 source:map[column:1071 line:20 type:source-location url:https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/static/js/common.bundle.min.js?ver=2024.5 urlProvider:network]] map[reflowTime:0.078 source:map[column:70434 line:1 type:source-location url:https://robbreport.com/wp-includes/js/jquery/jquery.min.js?ver=3.7.1 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.

URLResource SizeEst Savings
les colombieres menton article.editor-picks__secondary-pick > div.featured-image > a > img.attachment-featured-image-320x180
robbreport.com/wp-content/uploads/2026/04/lescolombieres.jpg?resize=681,38361.3 KiB49.0 KiB
magazine cover div.header-subscribe__container-inner > div.header-get__magazine-container > div.gtm-sub-cover > img.gtm-cover
/wp-content/uploads/2026/04/Untitled-design-6.png?w=150&h...25.5 KiB21.4 KiB
Bulgari Octo Finissimo, Jaeger-LeCoultre Master Control Perpetual Calendar, Par… article.editor-picks__secondary-pick > div.featured-image > a > img.attachment-featured-image-320x180
/wp-content/uploads/2026/04/RR_20260421_Watches_Wonders_E...27.5 KiB19.5 KiB

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.

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
cdn.tinypass.com/api/tinypass.min.js14400.0 s132.6 KiB
ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js14400.0 s132.2 KiB
connect.facebook.net/en_US/bundle/sdk.js/1200.0 s78.5 KiB
ads.blogherads.com/static/chunks/3622.7d0e84ccad5146cd86e6.js14400.0 s50.3 KiB
ads.blogherads.com/static/chunks/831.b113b40433677910de75.js14400.0 s43.1 KiB
ads.blogherads.com/static/chunks/2030.b94af747cd5b3350d333.js14400.0 s19.8 KiB
use.typekit.net/oxq7mos.js600.0 s8.9 KiB
ads.blogherads.com/static/chunks/982.31e834f3c5c91bf8b371.js14400.0 s11.5 KiB
pmc-pp-tou.s3.us-west-1.amazonaws.com/privacy-notice.js?ver=10.0 ms6.6 KiB
ads.blogherads.com/static/chunks/4857.910c4b46763f23e61854.js14400.0 s7.9 KiB
ads.blogherads.com/sk/00/000/00000/27336/header.js14400.0 s7.5 KiB
connect.facebook.net/en_US/sdk.js1200.0 s5.0 KiB
ads.blogherads.com/static/chunks/6559.074815d12fef9b41149e.js14400.0 s6.2 KiB
ads.blogherads.com/static/chunks/6317.7fde3be0f22be218a9d5.js14400.0 s5.0 KiB
ads.blogherads.com/static/blogherads.js14400.0 s4.2 KiB
cdn.keywee.co/dist/analytics-1.5.12.min.js259200.0 s7.9 KiB
rules.quantcount.com/rules-p-31f3D02tYU8zY.js3600.0 s1.7 KiB
d1mkq4fbm7j30i.cloudfront.net/21/oHS-21.js0.0 ms793 B
cmm.keywee.co/1146/main.min.js0.0 ms530 B
static.doubleclick.net/instream/ad_status.js900.0 s494 B
s3-us-west-2.amazonaws.com/jsstore/a/QKEH0ZG/ge.js0.0 ms425 B
cmm.keywee.co/1146/dist/aHR0cHM6Ly9yb2JicmVwb3J0LmNvbS8=.min.js0.0 ms386 B
iabusprivacy.pmc.com/geo-info.js0.0 ms265 B
ad-delivery.net/px.gif?ch=286400.0 s611 B
ad-delivery.net/px.gif?ch=186400.0 s109 B
/p.gif?s=1&k=oxq7mos&ht=tk&h=robbreport.com&f=31372.31373...604800.0 s205 B

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: 1.2 s
URLTime Spent
robbreport.com/1.3 s

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

TTI

Diagnostics

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

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

Why this matters

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

Learn more

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

Source: Google web.dev / Lighthouse

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

Max Potential First Input Delay 70 ms
Layout shift culprits
Optimize DOM size
LCP breakdown
LCP request discovery
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
JavaScript execution time 0.4 s
Minimizes main-thread work 1.3 s
Avoid long main-thread tasks 3 long tasks found
Image elements have explicit `width` and `height`
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 180 ms
Server Backend Latencies 150 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Avoid multiple page redirects
Avoid large layout shifts 1 layout shift found
INP breakdown
Avoid non-composited animations
85

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.

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
SHOP NOW div.gtm-sub-container > div.gtm-content > div > a.button
SUBSCRIBE div.gtm-sub-container > div.gtm-content > div > a.button

These are opportunities to improve the legibility of your content.

Names and labels

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
section.sectioner > div.footer-rr1_container > div.footer-rr1_video > iframe section.sectioner > div.footer-rr1_container > div.footer-rr1_video > 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.

Navigation

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

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
SUBSCRIBE header > div.header-inner > a.header-inner__subscribe > h3.header-inner__subscribe--header

These are opportunities to improve keyboard navigation in your application.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
head > meta head > 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
Image elements have `[alt]` attributes
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 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
Touch targets have sufficient size and spacing.
Document has a main landmark.
Deprecated ARIA roles were not used
`[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
`<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
Form elements have associated labels
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.
No element has a `[tabindex]` value greater than 0
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.
73

Best Practices

User Experience

Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.

Why this matters

Performance issues directly impact user engagement and conversion rates.

URLDisplayed sizeActual sizeExpected size
Children's lacrosse illustration article.editor-picks__primary-pick > div.featured-image > a > img.attachment-featured-image-980x551
/wp-content/uploads/2026/04/RR_Child_Athletics_1.jpg?resi...1140 x 641681 x 3831140 x 641

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
Topics

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
%cP%cM%cC Atlas MG padding: 2px 1px 2px 10px; border-radius: 7px 0 0 7px; background-color: black; color: white; padding: 2px 1px; background-color: black; color: #ed1c24; padding: 2px 10px 2px 1px; border-radius: 0 7px 7px 0; background-color: black; color: white; Error: Time to wait for consent has expired. at s (https://ads.blogherads.com/static/chunks/5273.eec6f62e6c9beefc4be4.js:2:106729) at Y (<anonymous>:1:2216)
ReferenceError: WebFont is not defined at Object.load (https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/assets/build/js/common.js?ver=1765796790:2:45831) at https://robbreport.com/wp-content/themes/pmc-robbreport-2017-v2/assets/build/js/common.js?ver=1765796790:2:45754 at Y (<anonymous>:1:2216)
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
Page has the HTML doctype
Properly defines charset
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 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
100

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.

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
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback