Netherlands · Amsterdam Completed: Apr 16, 2026 16:56 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 70 / 100
Based on 8 categories, 0 sections
Room to improve — your 25.5s load time is above Google's 2.5s 'Good' threshold.
Several missing protections leave your users and data exposed.
Several issues make your site difficult for assistive technology users.
Solid SEO basics — a few optimizations could boost rankings.
Good server performance with room for optimization.
Mostly compliant — a few items need attention.
Good content signals with minor gaps.
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.
1 button(s) with no accessible text
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
1 control(s) without accessible label
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
No <main> landmark found
Accessibility issues exclude users with disabilities — up to 15% of your potential audience.
High impact, low effort — start here.
High impact, requires investment.
Small gains, minimal effort.
Nothing in this quadrant — good news.
Low impact, high effort — do last.
Nothing in this quadrant — good news.
[](https://beavercheck.com/results/0f7c7aac-8173-44a8-9278-af91578ff581)<a href="https://beavercheck.com/results/0f7c7aac-8173-44a8-9278-af91578ff581"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Finstagram.com" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Finstagram.comThis badge auto-updates with your latest scan result.
Your site performs reasonably well, but a few targeted fixes could meaningfully improve results. Accessibility issues exclude users who rely on assistive technology — an estimated 15% of your potential audience. Addressing the critical issues below would have the most immediate impact on your user trust.
8 barrier(s) likely increasing bounce by ~30%.
Page takes 25.5s to load
+12% bounceUsers abandon at ~3s — you're 23.0s over the 2.5s threshold
Fix: Optimize render-blocking resources, preload the hero image, and compress images
Page feels frozen for 3.4s
+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
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
No skip-to-content link
+1% bounceKeyboard and screen-reader users must tab through the entire header on every page
Fix: Add a visible-on-focus <a href="#main">Skip to content</a> as the first focusable element
1 broken link(s) on the page
+2% bounceClicks 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.
$550 investment → $0.93/month returns + USD 157,500 risk avoided
$550
6h · 5 findings
$0.93 /mo
~$11 / year
USD 157,500
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.
5.5 developer hours at $100/hr
Based on United States rates ($100/hr)
Start here for the best return on investment
$13,126 / month at risk
~$157,511 / year if left unfixed
$157,500
+5 more
$0.93 /mo
11684.0 MB/mo × 0.080 USD/GB
Compliance figures represent the statutory maximum fine for the most severe triggered category, capped per regulation — not the sum of per-finding penalties. Based on published regulatory fine ranges. This is not legal advice.
Unique monthly visitors from your analytics
Purchases, signups, or key actions
Optional — for revenue estimation
more engaged visitors from reduced bounce
Fix 5 critical issues to capture this value
Based on Google/Deloitte research ("Milliseconds Make Millions") showing a ~7% bounce rate increase per additional second of LCP above the 2.5s "Good" threshold.
Your site's LCP: → estimated after fixes.
These are estimates based on industry research — actual results vary
Your data stays in your browser — nothing is sent to our servers
Thanks for your feedback!
We'll use a cached audit if available, or offer to scan.
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
4.46 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
25.48 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
3.43 s
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.059
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
5.28 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.
26.24 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.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
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 | |
|---|---|---|---|
Instagram div.x5n08af > div.x6s0dn4 > div.html-div > i | static.cdninstagram.com/rsrc.php/yC/r/SVLP5JBV4pG.webp | 991.5 KiB | 305.6 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.
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.
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| instagram.com/ | 847 ms |
| www.instagram.com/ | 0.0 ms |
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /rsrc.php/v5/yI/l/0,cross/NFX03JEm1Lb_jJK90a39bxNMm34SHFT... | 172.0 KiB | 167.8 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Performance issues directly impact user engagement and conversion rates.
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Performance issues directly impact user engagement and conversion rates.
| Category | Time Spent |
|---|---|
| Script Evaluation | 3.6 s |
| Script Parsing & Compilation | 2.3 s |
| Other | 1.9 s |
| Style & Layout | 756 ms |
| Parse HTML & CSS | 266 ms |
| Garbage Collection | 185 ms |
| Rendering | 56 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| 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 |
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 | |
|---|---|
from Meta main.xvbhtw8 > div.html-div > div.html-div > img | static.cdninstagram.com/rsrc.php/yb/r/SxCWlJznXoy.svg |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
head > meta#viewport head > meta#viewport |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | static.cdninstagram.com/rsrc.php/v4/y8/r/cqQl5CN3vO-.js line 238, col 362 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () |
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.
1.29 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.76 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
295 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
3.66 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.
4.36 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.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Performance issues directly impact user engagement and conversion rates.
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.
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 |
|---|---|
| static.cdninstagram.com/rsrc.php/yQ/r/-pkMfchyeAZ.woff2 | 20 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.x1ja2u2z > div.x9f619 > div.x9f619 > img.x15mokao div.x1ja2u2z > div.x9f619 > div.x9f619 > img.x15mokao | static.cdninstagram.com/rsrc.php/yJ/r/53X3pk-t2Gn.webp | 514.4 KiB | 470.7 KiB |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| instagram.com/ | 317 ms |
| www.instagram.com/ | 0.0 ms |
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Performance issues directly impact user engagement and conversion rates.
| URL | Time Spent |
|---|---|
| www.instagram.com/ | 1.7 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.
Performance issues directly impact user engagement and conversion rates.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Performance issues directly impact user engagement and conversion rates.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Performance issues directly impact user engagement and conversion rates.
| URL | Transfer Size | Est Savings |
|---|---|---|
| /rsrc.php/v5/yI/l/0,cross/NFX03JEm1Lb_jJK90a39bxPvJg89IT9... | 167.4 KiB | 162.5 KiB |
| :root, .__ig-light-mode:root, .__ig-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,… | 15.3 KiB | 10.2 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Multi-megabyte JavaScript bundles delay every interactive feature on the page.
This is the Lighthouse audit fired when too much JS is shipped relative to what executes. The fix isn't a config flag — it requires bundle analysis (webpack-bundle-analyzer, rollup-plugin-visualizer), splitting routes into chunks, lazy-loading off-screen components, and removing unused dependencies. Fundamentally different from minification: minifying reduces byte count, this reduces what's downloaded at all.
Source: Google web.dev / Lighthouse
| URL | Transfer Size | Est Savings |
|---|---|---|
| /rsrc.php/v4if1I4/yE/l/en_US/MrOObgNCOfEDc547MG6fL4170o3H... | 810.0 KiB | 521.1 KiB |
| /rsrc.php/v4iUz24/y4/l/en_US/GmByv9HsyxqTIhkBeJ1bvGsKSSRM... | 410.2 KiB | 357.8 KiB |
| /rsrc.php/v4iSXr4/yL/l/en_US/PzXQPG4s6aAxeEdcvYgHI_jKuXsx... | 364.4 KiB | 236.2 KiB |
| static.cdninstagram.com/rsrc.php/v4/yX/r/Qe-ItPPBtNW.js | 158.8 KiB | 149.0 KiB |
| static.cdninstagram.com/rsrc.php/v4idBq4/ye/l/en_US/rwXNf31RJQG.js | 76.8 KiB | 76.7 KiB |
| static.cdninstagram.com/rsrc.php/v4/yV/r/bluiyL1iuQr.js | 51.5 KiB | 49.7 KiB |
| static.cdninstagram.com/rsrc.php/v4/yN/r/TaoOhOefMWe.js | 40.6 KiB | 38.8 KiB |
| static.cdninstagram.com/rsrc.php/v4/y8/r/cqQl5CN3vO-.js | 72.1 KiB | 33.5 KiB |
| static.cdninstagram.com/rsrc.php/v4/yL/r/dIOoLgwar7h.js | 34.2 KiB | 31.6 KiB |
| /rsrc.php/v4iCLm4/yA/l/en_US/PUaa1AGUfcvmese8PpaA6YrvVQ59... | 28.7 KiB | 24.3 KiB |
| static.cdninstagram.com/rsrc.php/v4iwo24/yF/l/en_US/HI9jue3-BUf.js | 23.5 KiB | 22.1 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 |
|---|---|---|---|
| static.cdninstagram.com/rsrc.php/v4/y8/r/cqQl5CN3vO-.js | 891 ms | 764 ms | 20 ms |
| www.instagram.com/ | 402 ms | 23 ms | 0.2 ms |
| /rsrc.php/v4if1I4/yE/l/en_US/MrOObgNCOfEDc547MG6fL4170o3H... | 379 ms | 104 ms | 162 ms |
| /rsrc.php/v4iSXr4/yL/l/en_US/PzXQPG4s6aAxeEdcvYgHI_jKuXsx... | 204 ms | 82 ms | 81 ms |
| Unattributable | 160 ms | 15 ms | 0.0 ms |
| /rsrc.php/v4iUz24/y4/l/en_US/GmByv9HsyxqTIhkBeJ1bvGsKSSRM... | 101 ms | 7.8 ms | 93 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.0 s |
| Script Parsing & Compilation | 482 ms |
| Other | 421 ms |
| Style & Layout | 246 ms |
| Parse HTML & CSS | 88 ms |
| Garbage Collection | 31 ms |
| Rendering | 15 ms |
Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache
Performance issues directly impact user engagement and conversion rates.
| Failure reason | Failure type |
|---|---|
| The page has an unload handler in the main frame. | Actionable |
| Pages with cache-control:no-store header cannot enter back/forward cache. | Actionable |
| Pages that use WebAuthetication API are not eligible for back/forward cache. | Pending browser support |
| Chrome Password Manager was present upon navigating away. | Pending browser support |
| 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 |
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.
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.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html._9dls html._9dls |
These items highlight common accessibility best practices.
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Performance issues directly impact user engagement and conversion rates.
| Deprecation / Warning | Source |
|---|---|
| Unload event listeners are deprecated and will be removed. | static.cdninstagram.com/rsrc.php/v4/y8/r/cqQl5CN3vO-.js line 238, col 362 |
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Performance issues directly impact user engagement and conversion rates.
| Source | Description |
|---|---|
static.cdninstagram.com/rsrc.php/v4/y8/r/cqQl5CN3vO-.js line 78, col 566 | ErrorUtils caught an error:
[Caught in: Failed call to /ajax/bulk-route-definitions/: CometAyncFetchError: HTTP_CLIENT_ERROR..access-control-allow-credentials: true
access-control-allow-methods: OPTIONS
access-control-allow-origin: https://www.instagram.com
access-control-expose-headers: X-FB-Debug, X-Loader-Length, Error-MID, X-FB-Trace-ID, X-Stack
alt-svc: h3=":443"; ma=86400
cache-control: private, no-cache, no-store, must-revalidate
content-length: 0
content-security-policy: default-src *.facebook.com *.fbcdn.net *.instagram.com blob:;script-src *.instagram.com static.cdninstagram.com *.facebook.com *.fbcdn.net *.facebook.net 127.0.0.1:* 'nonce-Ww7iDi47' blob: 'self' 'wasm-unsafe-eval' https://*.google-analytics.com https://translate.google.com https://apis.google.com https://accounts.google.com;style-src *.instagram.com static.cdninstagram.com data: blob: 'unsafe-inline' *.fbcdn.net *.facebook.com https://accounts.google.com;connect-src *.instagram.com wss://edge-chat.instagram.com connect.facebook.net *.facebook.com facebook.com *.fbcdn.net *.facebook.net wss://*.facebook.com:* ws://localhost:* blob: *.cdninstagram.com wss://*.instagram.com:* 'self' https://accounts.google.com;font-src *.instagram.com static.cdninstagram.com data: *.fbcdn.net *.intern.facebook.com *.facebook.com https://fonts.gstatic.com;img-src *.instagram.com *.facebook.com *.fbcdn.net data: *.cdninstagram.com *.whatsapp.net blob: *.fbsbx.com android-webview-video-poster: *.oculuscdn.com *.giphy.com *.tenor.co *.tenor.com www.googleadservices.com *.doubleclick.net *.google.com *.google.co.uk https://www.gstatic.com https://*.google-analytics.com;media-src *.facebook.com *.fbcdn.net *.instagram.com *.cdninstagram.com *.fbsbx.com data: blob: https://*.giphy.com *.tenor.co *.tenor.com;child-src *.facebook.com *.fbcdn.net *.instagram.com data: blob:;frame-src *.instagram.com *.facebook.com *.fbsbx.com fbsbx.com data: www.googleadservices.com *.doubleclick.net *.google.com *.google.co.uk;manifest-src *.facebook.com *.fbcdn.net *.instagram.com data: blob:;object-src *.facebook.com *.fbcdn.net *.instagram.com data: blob:;block-all-mixed-content;upgrade-insecure-requests;
content-type: text/html; charset="utf-8"
cross-origin-opener-policy: same-origin-allow-popups
cross-origin-opener-policy-report-only: restrict-properties;report-to="coop_report"
cross-origin-resource-policy: same-site
date: Thu, 16 Apr 2026 16:55:50 GMT
document-policy: force-load-at-top, include-js-call-stacks-in-crash-reports
expires: Sat, 01 Jan 2000 00:00:00 GMT
origin-agent-cluster: ?1
origin-trial: ApxEQ+svJ/BvQ8JtSJdDsnwv/gOXedkcox0XU8+snS3w6b4nSgDoyEms+0jGopE4SIRVvlqJmzPHqZYbkP0sxwgAAAB1eyJvcmlnaW4iOiJodHRwczovL3d3dy5mYWNlYm9vay5jb206NDQzIiwiZmVhdHVyZSI6IkNyYXNoUmVwb3J0aW5nU3RvcmFnZUFQSSIsImV4cGlyeSI6MTc3NjcyOTYwMCwiaXNTdWJkb21haW4iOnRydWV9
permissions-policy: accelerometer=(self), attribution-reporting=(), autoplay=(), bluetooth=(), camera=(self), ch-device-memory=(), ch-downlink=(), ch-dpr=(), ch-ect=(), ch-rtt=(), ch-save-data=(), ch-ua-arch=(), ch-ua-bitness=(), ch-viewport-height=(), ch-viewport-width=(), ch-width=(), clipboard-read=(), clipboard-write=(self), compute-pressure=(), display-capture=(self), encrypted-media=(), fullscreen=(self), gamepad=(), geolocation=(self), gyroscope=(self), hid=(), idle-detection=(), interest-cohort=(), keyboard-map=(), local-fonts=(), magnetometer=(), microphone=(self), midi=(), otp-credentials=(self), payment=(), picture-in-picture=(self), private-state-token-issuance=(), publickey-credentials-get=(self "https://*.facebook.com" "https://facebook.com"), screen-wake-lock=(), serial=(), shared-storage=(), shared-storage-select-url=(), private-state-token-redemption=(), usb=(), unload=(self), window-management=(), xr-spatial-tracking=();report-to="permissions_policy"
pragma: no-cache
priority: u=1,i
proxy-status: http_request_error; e_fb_vipaddr="AcNUByRC3CdLPxfLzK6p5fVqy72lqvwXIJE2sIblbz3j_cUHjpg5GZRRbqMutHT-23ZDW8jK92Hq7GjwhiKHD9H4JT1nj2ZUdMoufOxl"; e_clientaddr="AcOM8pmKEAI6T4WpPhjMwAgofZgGbln3UoEYxi3kHkvjYzazRF2oV9G2GF2NfdU7MLdSkc_RuqdfFmKBpvHAyd5yHraRNJNjU3n1ORT3qi2TA3Kn_Q"; e_upip="AcOGVQFg8h25megUualZ3ECyPRKPseWbRyJSUZGN8fstxbjHKqSp-ZZ_c-g91e7koiWZqEXZk3MhfiZTJ6hNmhyVTOeKtqvzEnuMr5KLuAY"; e_fb_zone="AcOXpm8EvG8rjOEZgSDLklCC8rbxraqwHYLho0t93UXGmsyn5EiB_rjV-F-Bvsau"; e_fb_twtaskhandle="AcNzx-4WlTfoUlx4jQONRi6UvB4-kh6Cf5JBsXI8jhvpe5tfu5RD0rOvRe4PcZ7dr7tEXkH7Nqy7YBHNOLr41yK6v76NTSl3H7KMi79Zwg"; e_proxy="AcONaLAPH4PMCIbRu5q56SLqJcShJU_KhYqo945eqJgM-StUnX07Zu7DtRLwDw9dO7jmigAVFYwjvvwzVV0", http_request_error; e_fb_vipaddr="AcNOROp-HTRXa23_iWQbrZTQBj_bk4derEdZ3TdK1CGrj8RncgNIJ40LN8cNjvxYWfOF1ykQK_muze-XFix5fmM-gYGvy5AAy0KCDQ"; e_clientaddr="AcO_6rr-WuzB4ezvQP6PnvyfoqkakzpubmTTwnF5QhBhgs0aYkjykjicHcTCZjqy_7B3rkZpKdsK5H_MoTACuD8WpHY"; e_upip="AcNVMUXlOF9MAoncQnt9WZxl9j5O9NF5lTTZj3DGii_sMw7mGZ70SrSbN00mAKE8t6cYik0VJvhdfPQPtmBorBOSXa8d-DNOwgeu0s9o"; e_fb_zone="AcP3gjoidWNmYBiOYBtyx7_3vjMp9A9FBMwQShjxqQ89ptlY45OBqfbWN2B-Zg"; e_fb_twtaskhandle="AcN6V4drWlJxYl9Qt3uEFPk4lFhxtuZxsFbflmSDWxLLnyOTWHfPbJdGto6fv4yC0bTC8w9L_bwOLbcI2N3K4tMgLxogEv_0uecyeQ"; e_proxy="AcOMh4R7wedngsJ9LUyAayrzHQ-izlb427iFHg9jIRd7ahcs1ftYfY0f1f6Y8eNK8cnfZyORuh4_R9Q"
report-to: {"max_age":2592000,"endpoints":[{"url":"https:\/\/www.facebook.com\/browser_reporting\/coop\/?minimize=0"}],"group":"coop_report","include_subdomains":true}, {"max_age":259200,"endpoints":[{"url":"https:\/\/www.instagram.com\/error\/ig_web_error_reports\/?device_level=unknown&brsid=7629401878664350533&comet_app_key=7&cpp=C3&cv=1037486289&st=1776358550732"}]}
reporting-endpoints: coop_report="https://www.facebook.com/browser_reporting/coop/?minimize=0", default="https://www.instagram.com/error/ig_web_error_reports/?device_level=unknown&brsid=7629401878664350533&comet_app_key=7&cpp=C3&cv=1037486289&st=1776358550732"
strict-transport-security: max-age=31536000; preload; includeSubDomains
vary: Origin
x-content-type-options: nosniff
x-fb-connection-quality: EXCELLENT; q=0.9, rtt=1, rtx=0, c=60, mss=1232, tbw=163774, tp=205, tpl=0, uplat=109, ullat=0
x-fb-debug: EN4nQ4Ef+Vh4T/R/N0sKZE0b10QbFXHx68wjLh16z3DsrHwqRKcvRF89rdpr1+X5AlOj8xLk3SKL4GZcXCNVFQ==
x-frame-options: DENY
x-stack: www
x-xss-protection: 0
.XMLHttpRequest.HTTP 429.]
Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object] |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () | |
Failed to load resource: the server responded with a status of 429 () |
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