Singapore · Singapore Completed: Apr 21, 2026 23:14 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
Room to improve — your 10.0s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Mostly accessible, but some users still face barriers.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Strong compliance posture across regulations.
Rich content metadata — your pages look great everywhere.
Heavier than average — reducing page weight saves energy and bandwidth.
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
Security gaps expose your site and users to attacks, eroding trust.
No Content-Security-Policy header found
Security gaps expose your site and users to attacks, eroding trust.
Page weighs 7.4 MB (6.2 MB transferred)
Performance issues directly impact user engagement and conversion rates.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
35 third-party resources (100% of weight)
Performance issues directly impact user engagement and conversion rates.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/af4202eb-d4d3-4fb3-a2a5-e0db538281c3)<a href="https://beavercheck.com/results/af4202eb-d4d3-4fb3-a2a5-e0db538281c3"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fgeocaching.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fgeocaching.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Your LCP of 10.0s exceeds Google's 2.5s 'Good' threshold and the 2 performance issues below directly contribute to it. Addressing the critical issues below would have the most immediate impact on your user trust.
7 barrier(s) likely increasing bounce by ~30%.
Page takes 10.0s to load
+12% bounceUsers abandon at ~3s — you're 7.5s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 1.3s
+5% bounceClicks on the primary CTA are ignored while JavaScript runs
Fix: Break up long tasks; defer non-critical JavaScript to post-hydration
No Content-Security-Policy header
+1% bounceHigher XSS blast radius — one compromised script can exfiltrate the checkout form
Fix: Ship a reporting-only CSP first, then enforce once violations are clean
Layout shifts during page load
+3% bounceContent movement causes mis-clicks on CTAs and form fields
Fix: Add width/height to images; reserve space for late-loading embeds
1 form field(s) without a label
+2% bounceScreen readers skip unlabeled fields; autofill can't identify them; checkout abandonment spikes
Fix: Associate every input with a visible <label for="…">; add autocomplete attributes
No structured data
+2% bounceNo rich-result eligibility in Google — lower SERP CTR vs competitors with stars and prices
Fix: Add JSON-LD for your page type (Product, Article, FAQPage, LocalBusiness, …)
Thin content
+3% bounceUnder 300 words — visitors bounce looking for substance, search engines rank competitors first
Fix: Add a substantive FAQ, product detail, or case-study section
Preliminary CRO audit — each barrier links to the tab with detailed analysis.
$650 investment → $5,485/month returns + USD 150,000 risk avoided
$650
6h · 5 findings
$5,485 /mo
~$65,823 / year
USD 150,000
if kept compliant
$100 — in quick wins — start here for the fastest payback
Figures combine localized regulatory fine ceilings, search/conversion value priced against local CPC, and bandwidth waste estimates. Results depend on implementation quality and audience composition. Not legal or financial advice.
6.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$12,502 / month at risk
~$150,019 / year if left unfixed
$150,000
$1.56 /mo
19442.2 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 4 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
4.55 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
10.03 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
1.31 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.155
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.98 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.
22.96 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.geocaching.com/play/app/ui-scss/lohp-layout.css | 6.1 KiB | 333 ms |
| fonts.googleapis.com/css?family=Noto+Sans:400,700&subset=latin,greek-ext | 1.2 KiB | 760 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| d17wd0umvxxjds.cloudfront.net/play/Content/videos/loggedout-cache-finds.webm | 0.0 ms | 2.9 MiB |
| /play/bundles/lohp?v=kHsKCzo5KyezTAmR6roZlrVfiTR7mXqKh1iF... | 0.0 ms | 2.4 MiB |
| static.hotjar.com/c/hotjar-441815.js?sv=7 | 60.0 s | 6.2 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /s/notosans/v42/o-0bIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjc5a7du... | 5.0 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner | d1gkberomxrum0.cloudfront.net/2017/09/05125108/containers-416x150.png | 115.1 KiB | 105.0 KiB |
div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner | d1gkberomxrum0.cloudfront.net/2017/07/12153715/whatsnew.png | 114.9 KiB | 104.8 KiB |
div.inner > div.phone > div#phone-map-wrapper > img#default-map-img div.inner > div.phone > div#phone-map-wrapper > img#default-map-img | www.geocaching.com/play/Content/images/lohp/map-screens-small/en-US.jpg | 23.7 KiB | 16.0 KiB |
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| geocaching.com/ | 1.3 s |
| www.geocaching.com/ | 1.3 s |
| www.geocaching.com/play | 0.0 ms |
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Performance issues directly impact user engagement and conversion rates.
| Element | Layout shift score |
|---|---|
There are 1,165 geocaches around Singapore.
To get started, create a free geoc… main#Content > section.app-section > div.inner > div.content | 0.155 |
Geocaching body.lohp > header.page-header > div.logo-wrapper | 0.001 |
English
English
Български
Català
Čeština
Dansk
Deutsch
Ελληνικά
Eesti
Español
… body.lohp > header.page-header > nav | 0.000 |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /play/bundles/lohp?v=kHsKCzo5KyezTAmR6roZlrVfiTR7mXqKh1iF... | 2.4 MiB | 1.8 MiB |
| www.googletagmanager.com/gtag/js?id=G-GRQE2910DL&cx=c>m=4e64h1h1 | 144.1 KiB | 63.2 KiB |
| www.googletagmanager.com/gtag/js?id=G-WH86DS6J89&cx=c>m=4e64h1h1 | 160.9 KiB | 58.7 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-N3KS8V2 | 138.8 KiB | 54.6 KiB |
| script.hotjar.com/modules.6a0f3932cb1341a35c18.js | 56.1 KiB | 37.2 KiB |
| www.geocaching.com/play/app/dist/7029.f5556649571538f1018f.js | 27.4 KiB | 21.3 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.
Performance issues directly impact user engagement and conversion rates.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| Unattributable | 721 ms | 18 ms | 0.0 ms |
| /play/bundles/lohp?v=kHsKCzo5KyezTAmR6roZlrVfiTR7mXqKh1iF... | 700 ms | 279 ms | 389 ms |
| www.googletagmanager.com/gtm.js?id=GTM-N3KS8V2 | 457 ms | 373 ms | 66 ms |
| www.googletagmanager.com/gtag/js?id=G-WH86DS6J89&cx=c>m=4e64h1h1 | 414 ms | 343 ms | 66 ms |
| www.geocaching.com/play | 353 ms | 9.7 ms | 3.4 ms |
| www.googletagmanager.com/gtag/js?id=G-GRQE2910DL&cx=c>m=4e64h1h1 | 293 ms | 234 ms | 57 ms |
| www.geocaching.com/play/app/dist/5609.c446c261e0f64313b59c.js | 269 ms | 267 ms | 1.3 ms |
| script.hotjar.com/modules.6a0f3932cb1341a35c18.js | 200 ms | 165 ms | 31 ms |
| www.geocaching.com/play/app/dist/4254.00132854dc3d5de4d886.js | 88 ms | 84 ms | 2.0 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
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.8 s |
| Other | 752 ms |
| Script Parsing & Compilation | 648 ms |
| Style & Layout | 239 ms |
| Rendering | 63 ms |
| Garbage Collection | 41 ms |
| Parse HTML & CSS | 23 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .sr-only { position: absolute !important; width: 1px !important; height: 1px !important; … } … | 19.3 KiB | 18.3 KiB |
| :root{--color-bg-action-banner-success:#e6faeb;--color-bg-app:#f5f5f5;--color-bg-compass:#00663d;--… | 18.4 KiB | 16.7 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
section.app-section > div.inner > div.phone > img.phone-image section.app-section > div.inner > div.phone > img.phone-image | www.geocaching.com/play/Content/images/lohp/phoneframe.png |
div.inner > div.phone > div#phone-map-wrapper > img#default-map-img div.inner > div.phone > div#phone-map-wrapper > img#default-map-img | www.geocaching.com/play/Content/images/lohp/map-screens-small/en-US.jpg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English
Български
Català
Čeština
Dansk
Deutsch
Ελληνικά
Eesti
Español
Français
… nav > div#header-language-select > div.language-dropdown > select |
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.
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Performance issues directly impact user engagement and conversion rates.
| URL | Displayed size | Actual size | Expected size | |
|---|---|---|---|---|
section.app-section > div.inner > div.phone > img.phone-image section.app-section > div.inner > div.phone > img.phone-image | www.geocaching.com/play/Content/images/lohp/phoneframe.png | 226 x 382 | 226 x 382 | 339 x 573 |
div.inner > div.phone > div#phone-map-wrapper > img#default-map-img div.inner > div.phone > div#phone-map-wrapper > img#default-map-img | www.geocaching.com/play/Content/images/lohp/map-screens-small/en-US.jpg | 164 x 288 | 164 x 288 | 246 x 432 |
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.13 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.55 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
150 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.038
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.81 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.
5.84 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Performance issues directly impact user engagement and conversion rates.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
Shipping ES5 transpiled code to modern browsers wastes bytes — every user with an evergreen browser pays for compatibility you don't need.
Most users today run browsers that natively support ES6+, async/await, optional chaining, and the rest of modern JavaScript. Transpiling to ES5 'just in case' adds 20-40% to your bundle for no benefit. Configure your build to target a modern browserslist, or ship a differential bundle pair (modern + legacy) with the module/nomodule pattern.
Source: Google web.dev / Lighthouse
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
Performance issues directly impact user engagement and conversion rates.
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Performance issues directly impact user engagement and conversion rates.
Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays.
Performance issues directly impact user engagement and conversion rates.
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
Performance issues directly impact user engagement and conversion rates.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Performance issues directly impact user engagement and conversion rates.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Duration |
|---|---|---|
| www.geocaching.com/play/app/ui-scss/lohp-layout.css | 6.1 KiB | 224 ms |
| fonts.googleapis.com/css?family=Noto+Sans:400,700&subset=latin,greek-ext | 1.2 KiB | 207 ms |
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
Performance issues directly impact user engagement and conversion rates.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| d17wd0umvxxjds.cloudfront.net/play/Content/videos/loggedout-cache-finds.webm | 0.0 ms | 2.9 MiB |
| /play/bundles/lohp?v=kHsKCzo5KyezTAmR6roZlrVfiTR7mXqKh1iF... | 0.0 ms | 2.4 MiB |
| static.hotjar.com/c/hotjar-441815.js?sv=7 | 60.0 s | 6.3 KiB |
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.
Performance issues directly impact user engagement and conversion rates.
| URL | Est Savings |
|---|---|
| /s/notosans/v42/o-0bIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjc5a7du... | 10 ms |
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
Performance issues directly impact user engagement and conversion rates.
| URL | Resource Size | Est Savings | |
|---|---|---|---|
div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner | d1gkberomxrum0.cloudfront.net/2017/09/05125108/containers-416x150.png | 115.1 KiB | 105.0 KiB |
div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner div.whats-new > div.whats-new-item > a.article-tile > span.whats-new-banner | d1gkberomxrum0.cloudfront.net/2017/07/12153715/whatsnew.png | 114.9 KiB | 104.8 KiB |
div.inner > div.phone > div#phone-map-wrapper > img#default-map-img div.inner > div.phone > div#phone-map-wrapper > img#default-map-img | www.geocaching.com/play/Content/images/lohp/map-screens-small/en-US.jpg | 23.7 KiB | 16.0 KiB |
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
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.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| geocaching.com/ | 730 ms |
| www.geocaching.com/ | 728 ms |
| www.geocaching.com/play | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /play/bundles/lohp?v=kHsKCzo5KyezTAmR6roZlrVfiTR7mXqKh1iF... | 2.4 MiB | 1.8 MiB |
| www.googletagmanager.com/gtag/js?id=G-GRQE2910DL&cx=c>m=4e64h1 | 144.1 KiB | 62.5 KiB |
| www.googletagmanager.com/gtag/js?id=G-WH86DS6J89&cx=c>m=4e64h1 | 160.9 KiB | 58.4 KiB |
| www.googletagmanager.com/gtm.js?id=GTM-N3KS8V2 | 138.8 KiB | 54.6 KiB |
| script.hotjar.com/modules.6a0f3932cb1341a35c18.js | 56.1 KiB | 37.2 KiB |
| www.geocaching.com/play/app/dist/7029.f5556649571538f1018f.js | 27.4 KiB | 21.3 KiB |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages whose main resource has cache-control:no-store cannot enter back/forward cache. | Not actionable |
| Back/forward cache is disabled because some JavaScript network request received resource with Cache-Control: no-store header. | Not actionable |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| .sr-only { position: absolute !important; width: 1px !important; height: 1px !important; … } … | 19.3 KiB | 18.1 KiB |
| :root{--color-bg-action-banner-success:#e6faeb;--color-bg-app:#f5f5f5;--color-bg-compass:#00663d;--… | 18.4 KiB | 16.5 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Performance issues directly impact user engagement and conversion rates.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Performance issues directly impact user engagement and conversion rates.
| URL | |
|---|---|
section.app-section > div.inner > div.phone > img.phone-image section.app-section > div.inner > div.phone > img.phone-image | www.geocaching.com/play/Content/images/lohp/phoneframe.png |
div.inner > div.phone > div#phone-map-wrapper > img#default-map-img div.inner > div.phone > div#phone-map-wrapper > img#default-map-img | www.geocaching.com/play/Content/images/lohp/map-screens-small/en-US.jpg |
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
English
Български
Català
Čeština
Dansk
Deutsch
Ελληνικά
Eesti
Español
Français
… nav > div#header-language-select > div.language-dropdown > select |
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.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Performance issues directly impact user engagement and conversion rates.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Send Feedback