C — https://www.instagram.com

Site Health

Score: 74 / 100

Based on 8 categories, 0 sections

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.

Top Priorities (5)

'unsafe-eval' found in script source

Security › Content Security Policy

1 button(s) with no accessible text

Accessibility › Link & Button Quality

1 control(s) without accessible label

Accessibility › Form Accessibility

No <main> landmark found

Accessibility › Landmark Structure

Certificate expires soon (8 days remaining)

Security › TLS & Certificates

Embed this badge

Markdown

[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.instagram.com)](https://beavercheck.com/results/03697ac7-66cf-4948-969c-c56eb41b329f)

HTML

<a href="https://beavercheck.com/results/03697ac7-66cf-4948-969c-c56eb41b329f"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.instagram.com" alt="BeaverCheck Score"></a>

Image URL

https://beavercheck.com/badge?url=https%3A%2F%2Fwww.instagram.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Press ? for shortcuts

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

Performance

Accessibility

Best Practices

100

SEO

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.

1.79 s

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

23.18 s

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

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

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

23.29 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

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

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

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.

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:0.602 source:map[column:1634 line:245 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js urlProvider:network]]]

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:67.464 source:map[type:text value:[unattributed]]] map[reflowTime:0.602 source:map[column:323 line:1563 type:source-location url:https://static.cdninstagram.com/rsrc.php/v4i53V4/y_/l/en_US/UbHRbbu77fGjLEwhnD36Ge82perklV9DJBMu4qonYA1T2mqBBUHA2Fi8JriexMzqPrAaDuivcDRuKoKGVUPWEs-dqHn7WPVnsii2Un3tEbQ1Cawy6TOoSQVo_p4fn1Iw4pEdnAdTcUuKOIvIzb-dcO57g8B2fZxBO4vmAxeEdcvYgHI_fEXKxzJbolxY4WUnhUXRYJ1DAKUoGsim5BSzYMNqp2HZxslnTDalIH_zrwlxJzwovg7hFx3Yi0Aq1LXlhXPQd0TcdiTtvrA0TVf_vnwh3ABvYCP-eMJu6WuEh_DQo6mNz8dfZ2Gu4dbtEj8UfWop6x9DjN.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

	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.

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

value: no origins were preconnected

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

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.

TTI

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

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.

Estimated savings: 900 ms 147.6 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/yO/l/0,cross/q7A6Qm8E9uKcMj9RuHJmLGNMm34SHFT...	151.7 KiB	147.6 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.

Estimated savings: 10.5 s 1.9 MiB

URL	Transfer Size	Est Savings
/rsrc.php/v4i53V4/y_/l/en_US/UbHRbbu77fGjLEwhnD36Ge82perk...	810.7 KiB	581.6 KiB
/rsrc.php/v4ilPZ4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...	486.0 KiB	302.3 KiB
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js	158.5 KiB	148.7 KiB
/rsrc.php/v4ipFP4/y0/l/en_US/VVBgXoGhzYn3zggH72LrtgrrCxjE...	120.9 KiB	112.0 KiB
static.cdninstagram.com/rsrc.php/v4itz-4/y8/l/en_US/j3F-n2bpeEd.js	121.6 KiB	107.4 KiB
/rsrc.php/v4ieFP4/yG/l/en_US/spZdStSQuQoGZUyO6OuMq8fT6yKH...	112.1 KiB	99.4 KiB
/rsrc.php/v4ikaU4/y1/l/en_US/7ZML0akupg0kbF2CakavQ57mttmL...	135.7 KiB	99.3 KiB
static.cdninstagram.com/rsrc.php/v4idBq4/ye/l/en_US/rwXNf31RJQG.js	76.8 KiB	76.6 KiB
static.cdninstagram.com/rsrc.php/v4/yf/r/GzNwqbjlXiu.js	78.2 KiB	71.8 KiB
static.cdninstagram.com/rsrc.php/v4ie3F4/yj/l/en_US/bPBcfilPiNd.js	71.3 KiB	64.5 KiB
static.cdninstagram.com/rsrc.php/v4iVv04/y7/l/en_US/g4x5GkmyDIO.js	57.2 KiB	53.2 KiB
static.cdninstagram.com/rsrc.php/v4/yw/r/0SuBtElp2rI.js	44.0 KiB	42.9 KiB
static.cdninstagram.com/rsrc.php/v4ijWG4/yv/l/en_US/6BQcE_IsJJs.js	49.8 KiB	39.2 KiB
static.cdninstagram.com/rsrc.php/v4/yR/r/Ve24ViYIrgR.js	40.4 KiB	38.7 KiB
static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js	74.0 KiB	38.4 KiB
static.cdninstagram.com/rsrc.php/v4/yr/r/H_AD9smLz73.js	34.7 KiB	32.1 KiB
static.cdninstagram.com/rsrc.php/v4/yB/r/GFI39NwSgLx.js	24.9 KiB	24.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.

URL	Total CPU Time	Script Evaluation	Script Parse
static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js	2.3 s	2.0 s	60 ms
/rsrc.php/v4i53V4/y_/l/en_US/UbHRbbu77fGjLEwhnD36Ge82perk...	656 ms	90 ms	516 ms
www.instagram.com/	631 ms	42 ms	0.7 ms
/rsrc.php/v4ilPZ4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...	608 ms	35 ms	317 ms
Unattributable	404 ms	32 ms	0.0 ms
	168 ms	87 ms	51 ms
/rsrc.php/v4ikaU4/y1/l/en_US/7ZML0akupg0kbF2CakavQ57mttmL...	134 ms	15 ms	118 ms
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js	103 ms	7.6 ms	95 ms
static.cdninstagram.com/rsrc.php/v4itz-4/y8/l/en_US/j3F-n2bpeEd.js	90 ms	11 ms	78 ms
/rsrc.php/v4ipFP4/y0/l/en_US/VVBgXoGhzYn3zggH72LrtgrrCxjE...	74 ms	5.6 ms	68 ms
/rsrc.php/v5/yO/l/0,cross/q7A6Qm8E9uKcMj9RuHJmLGNMm34SHFT...	74 ms	0.0 ms	0.0 ms
/rsrc.php/v4ieFP4/yG/l/en_US/spZdStSQuQoGZUyO6OuMq8fT6yKH...	71 ms	5.6 ms	59 ms
static.cdninstagram.com/rsrc.php/v4ie3F4/yj/l/en_US/bPBcfilPiNd.js	58 ms	3.6 ms	54 ms
static.cdninstagram.com/rsrc.php/v4/yf/r/GzNwqbjlXiu.js	57 ms	3.9 ms	53 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

Category	Time Spent
Script Evaluation	2.4 s
Script Parsing & Compilation	1.7 s
Other	894 ms
Style & Layout	452 ms
Parse HTML & CSS	173 ms
Garbage Collection	152 ms
Rendering	22 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

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.

URL	Transfer Size
static.cdninstagram.com/rsrc.php/yC/r/SVLP5JBV4pG.webp	991.7 KiB
/rsrc.php/v4i53V4/y_/l/en_US/UbHRbbu77fGjLEwhnD36Ge82perk...	810.9 KiB
/rsrc.php/v4ilPZ4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...	486.2 KiB
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js	158.6 KiB
/rsrc.php/v5/yO/l/0,cross/q7A6Qm8E9uKcMj9RuHJmLGNMm34SHFT...	151.9 KiB
/rsrc.php/v4ikaU4/y1/l/en_US/7ZML0akupg0kbF2CakavQ57mttmL...	135.8 KiB
www.instagram.com/	135.0 KiB
static.cdninstagram.com/rsrc.php/v4itz-4/y8/l/en_US/j3F-n2bpeEd.js	121.7 KiB
/rsrc.php/v4ipFP4/y0/l/en_US/VVBgXoGhzYn3zggH72LrtgrrCxjE...	121.0 KiB
/rsrc.php/v4ieFP4/yG/l/en_US/spZdStSQuQoGZUyO6OuMq8fT6yKH...	112.2 KiB

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

	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.

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●Font display

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 65 user timings

●Avoid long main-thread tasks 20 long tasks found

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 190 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 280 ms

●Avoid large layout shifts 1 layout shift found

○INP breakdown

○LCP request discovery

○Avoid non-composited animations

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.

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.

Failing Elements
head > meta#viewport `head > meta#viewport`

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

●Select elements have associated label elements.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○`<frame>` or `<iframe>` elements have a title

○`<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

○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

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js line 251, 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

Source	Description
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`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.

URL
static.cdninstagram.com/rsrc.php/v4itz-4/y8/l/en_US/j3F-n2bpeEd.js
/rsrc.php/v4ilPZ4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...
/rsrc.php/v4ikaU4/y1/l/en_US/7ZML0akupg0kbF2CakavQ57mttmL...
/rsrc.php/v4i53V4/y_/l/en_US/UbHRbbu77fGjLEwhnD36Ge82perk...
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js

●Uses HTTPS

●Avoids third-party cookies

●Allows users to paste into input fields

●Avoids requesting the geolocation permission on page load

●Avoids requesting the notification permission on page load

●Displays images with correct aspect ratio

●Serves images with appropriate resolution

●Page has the HTML doctype

●Properly defines charset

●No issues in the `Issues` panel in Chrome Devtools

●Ensure CSP is effective against XSS attacks

●Ensure proper origin isolation with COOP

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

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

Performance

Accessibility

Best Practices

100

SEO

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.

1.01 s

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

3.51 s

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

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

1.53 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.53 s

Detailed Report

Audit breakdown by category with detailed findings.

Performance

Insights

Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.

3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.

headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]

items: [map[reflowTime:93.504 source:map[type:text value:[unattributed]]]]

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

lhId: page-0-IMG

nodeLabel: div.x1ja2u2z > div.x9f619 > div.x9f619 > img.x15mokao

path: 1,HTML,1,BODY,2,DIV,2,DIV,1,DIV,2,DIV,0,DIV,0,DIV,1,DIV,1,DIV,1,DIV,0,DIV,0,DIV,0,DIV,0,DIV,0,DIV,2,DIV,0,DIV,0,DIV,1,IMG

selector: div.x1ja2u2z > div.x9f619 > div.x9f619 > img.x15mokao

snippet: <img class="x15mokao x1ga7v0g x16uus16 xbiv7yw x3j1f2j xqb9ast x1htk8sl x19kjcj4 x1bcv…" alt="" referrerpolicy="origin-when-cross-origin" src="https://static.cdninstagram.com/rsrc.php/yN/r/-erGonz07kB.webp">

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.

title: Preconnected origins

value: no origins were preconnected

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

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.

URL	Est Savings
static.cdninstagram.com/rsrc.php/yQ/r/-pkMfchyeAZ.woff2	15 ms

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

	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/yN/r/-erGonz07kB.webp	563.2 KiB	519.4 KiB

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

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

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.

Estimated savings: 160 ms 153.0 KiB

URL	Transfer Size	Est Savings
/rsrc.php/v5/yj/l/0,cross/q7A6Qm8E9uKcMj9RuHJmLGPvJg89IT9...	147.3 KiB	142.7 KiB
:root, .__ig-light-mode:root, .__ig-light-mode {--fds-black:#000000;--fds-black-alpha-05:rgba(0, 0,…	15.5 KiB	10.3 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.

Estimated savings: 1.2 s 1.5 MiB

URL	Transfer Size	Est Savings
/rsrc.php/v4iDqw4/yR/l/en_US/82perklV9DJBMu4qonYA1T2mqBBU...	728.3 KiB	537.4 KiB
/rsrc.php/v4iXCl4/yB/l/en_US/ZSzYR14k9w9jLEwhnD36Ge6BQcE_...	399.5 KiB	351.8 KiB
/rsrc.php/v4idqz4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...	419.7 KiB	218.7 KiB
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js	158.5 KiB	148.7 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/yu/r/u9HAKJpT99D.js	59.8 KiB	57.6 KiB
static.cdninstagram.com/rsrc.php/v4/yR/r/Ve24ViYIrgR.js	40.4 KiB	38.6 KiB
static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js	74.0 KiB	35.5 KiB
static.cdninstagram.com/rsrc.php/v4/yr/r/H_AD9smLz73.js	34.7 KiB	32.1 KiB
/rsrc.php/v4iija4/yQ/l/en_US/d4u9RG6sxvDWLEKM8Y4pNee4gHWv...	34.8 KiB	31.2 KiB
/rsrc.php/v4iT6l4/yU/l/en_US/l3kuim2Ho1EOVLE6s-6C-mv_RBel...	59.4 KiB	25.0 KiB
static.cdninstagram.com/rsrc.php/v4irPe4/yq/l/en_US/Y4WUnhUXRYJ.js	23.6 KiB	22.1 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

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.

URL	Transfer Size
/rsrc.php/v4iDqw4/yR/l/en_US/82perklV9DJBMu4qonYA1T2mqBBU...	728.4 KiB
static.cdninstagram.com/rsrc.php/yN/r/-erGonz07kB.webp	563.3 KiB
/rsrc.php/v4idqz4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...	419.8 KiB
/rsrc.php/v4iXCl4/yB/l/en_US/ZSzYR14k9w9jLEwhnD36Ge6BQcE_...	399.6 KiB
static.cdninstagram.com/rsrc.php/yQ/r/-pkMfchyeAZ.woff2	179.1 KiB
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js	158.6 KiB
/rsrc.php/v5/yj/l/0,cross/q7A6Qm8E9uKcMj9RuHJmLGPvJg89IT9...	147.5 KiB
www.instagram.com/	121.8 KiB
static.cdninstagram.com/rsrc.php/v4idBq4/ye/l/en_US/rwXNf31RJQG.js	77.0 KiB
static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js	74.1 KiB

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

●Max Potential First Input Delay 120 ms

●Use efficient cache lifetimes

●Layout shift culprits

●Document request latency

●Optimize DOM size

●LCP breakdown

●Modern HTTP

●Render blocking requests

●Optimize viewport for mobile

●Minify CSS

●Minify JavaScript

●User Timing marks and measures 85 user timings

●JavaScript execution time 0.9 s

●Minimizes main-thread work 1.5 s

●Avoid long main-thread tasks 5 long tasks found

●Image elements have explicit `width` and `height`

●Network Requests

●Network Round Trip Times 10 ms

●Server Backend Latencies 180 ms

●Tasks

●Diagnostics

●Metrics

●Screenshot Thumbnails

●Final Screenshot

●Script Treemap Data

●Resources Summary

●Avoid multiple page redirects

●Initial server response time was short Root document took 230 ms

●Avoid large layout shifts 2 layout shifts found

○INP breakdown

○Avoid non-composited animations

Accessibility

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Failing Elements
html._9dls `html._9dls`

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

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●Select elements have associated label elements.

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

○`<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

○`<frame>` or `<iframe>` elements have a title

○Heading elements appear in a sequentially-descending order

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○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

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

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

Best Practices

General

Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.

Deprecation / Warning	Source
Unload event listeners are deprecated and will be removed.	static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js line 251, 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

Source	Description
static.cdninstagram.com/rsrc.php/v4/ya/r/R1pEz0OuWy4.js line 78, col 566	`ErrorUtils caught an error: Unable to resolve resource PMh1QI7. Subsequent non-fatal errors won't be logged; see https://fburl.com/debugjs. [object Object]`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`
www.instagram.com/ajax/bulk-route-definitions/	`Failed to load resource: the server responded with a status of 429 ()`

URL
/rsrc.php/v4iXCl4/yB/l/en_US/ZSzYR14k9w9jLEwhnD36Ge6BQcE_...
/rsrc.php/v4idqz4/yP/l/en_US/k_wk718FR3gDSW1P86M9RR5-cZF6...
/rsrc.php/v4iDqw4/yR/l/en_US/82perklV9DJBMu4qonYA1T2mqBBU...
static.cdninstagram.com/rsrc.php/v4/yB/r/ny_ONvAlbQE.js

●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

●Mitigate DOM-based XSS with Trusted Types

○Redirects HTTP traffic to HTTPS

○Use a strong HSTS policy

○Ensure proper origin isolation with COOP

○Mitigate clickjacking with XFO or CSP

○Detected JavaScript libraries

100

SEO

○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`

Results for https://www.instagram.com

Site Health

Top Priorities (5)

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Lighthouse Scores

Core Web Vitals

Detailed Report

Performance

Insights

Diagnostics

Accessibility

Best practices

Best Practices

General

SEO

Keyboard Shortcuts