Total
1.55 MB
71 requests
100% of total size
Screenshot captured after 6.68 s.
Ağlarken Yakalanan Megan Fox (2007) - YouTube
See the website health and performance test results for https://www.youtube.com/shorts/iI7kyVaNudI, including status code, load speed, SSL, WHOIS, DNS, console logs, Chrome UX Report, resource sizes, and Pagespeed findings.
Tested on 20 Apr 2026 19:15:32.
Up
- HTTP status 200
- Response time 2.29 s
- Document load time 194 ms
- Full page load time 6.68 s
- Document size 1.05 MB
- Full page size 593.66 KB
16/100
- Mobile score 16
- Desktop score 9
Did you know?
Observer tracks these signals every day and alerts you the moment something important changes. Register now.
15 Feb 2027
270 days left
22 Jun 2026
32 days left
Whois
- Registrar
- MarkMonitor, Inc.
- Created
- 15 Feb 2005
- Updated
- 14 Jan 2026
- Expires
- 15 Feb 2027
- Country
- US
- DNSSEC
- unsigned
SSL
- Issuer
- C=US,O=Google Trust Services,CN=WE2
- Subject
- CN=*.google.com
- TLS version
- TLSv1.3
- Self-signed
- No
- Valid until
- 22 Jun 2026
DNS Records
Current DNS records returned for this domain at the time of the test.
- 192.178.24.14
- 192.178.24.46
- 172.217.20.78
- 172.217.23.142
- 172.217.16.142
- 192.178.24.78
- 172.217.171.78
- 216.58.204.110
- 172.217.23.14
- 192.178.24.174
- 142.251.142.110
- 192.178.25.238
- 172.217.21.238
- 172.217.20.206
- 172.217.22.238
- 142.251.38.238
- 2a00:1450:4017:819::200e
- 2a00:1450:4017:824::200e
- 2a00:1450:4017:817::200e
- 2a00:1450:4017:821::200e
- youtube-ui.l.google.com
No records returned.
No records returned.
No records returned.
Resource Summary
Transfer size share of the tested page split by resource type.
Script
1016.24 KB
13 requests
64% of total size
Document
252.74 KB
2 requests
16% of total size
Stylesheet
180 KB
2 requests
11% of total size
Other
51.63 KB
45 requests
3.3% of total size
Font
29.72 KB
2 requests
1.9% of total size
Media
28.29 KB
4 requests
1.8% of total size
Image
23.92 KB
3 requests
1.5% of total size
Third-party
1.55 MB
71 requests
100% of total size
Total
3.56 MB
154 requests
100% of total size
Script
2.54 MB
15 requests
71% of total size
Stylesheet
352.66 KB
8 requests
9.7% of total size
Document
279.24 KB
2 requests
7.7% of total size
Image
198.37 KB
15 requests
5.4% of total size
Other
119.38 KB
108 requests
3.3% of total size
Font
62.1 KB
2 requests
1.7% of total size
Media
28.29 KB
4 requests
0.8% of total size
Third-party
3.56 MB
154 requests
100% of total size
Core Web Vitals
Key performance signals from Lighthouse, with color-coded status for what is healthy and what still needs work.
The server starts responding quickly.
First visible content is slower than recommended.
Main visible content takes too long to appear.
Layout shifts are high and likely disruptive.
Visual loading is significantly delayed.
Heavy blocking is likely hurting responsiveness.
Potential input delay is high.
Users wait too long before the page responds.
TTFB
601 ms
FCP
2.71 s
LCP
7.54 s
TTI
12.2 s
The server starts responding quickly.
First visible content is slower than recommended.
Main visible content takes too long to appear.
Layout shifts are high and likely disruptive.
Visual progress is slower than recommended.
Heavy blocking is likely hurting responsiveness.
Potential input delay is high.
Users wait too long before the page responds.
TTFB
161 ms
FCP
2.01 s
LCP
6.19 s
TTI
8.46 s
Loading Filmstrip
Visual loading progress from the Lighthouse run, shown in time order.
Google Pagespeed Insights
Switch between desktop and mobile Lighthouse results to review the latest performance findings for this page.
Mobile
16
Desktop
9
Audit Details
| Audit | Insight | Impact |
|---|---|---|
| Minimize main-thread work | 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 | 4.8 s |
| Reduce JavaScript execution time | 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.
| 2.7 s |
| Document request latency | Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression. | Est savings of 1,290 ms |
| Reduce unused JavaScript | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| Est savings of 575 KiB |
| Reduce unused CSS | 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.
| Est savings of 176 KiB |
| Reduce initial server response time | 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.
| Root document took 1,350 ms |
| Avoid multiple page redirects | Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| Est savings of 750 ms |
| Render blocking requests | 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.
| Est savings of 850 ms |
| Avoid large layout shifts | 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
| 2 layout shifts found |
| Layout shift culprits | 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. | Open |
| Network dependency tree | 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. | Open |
| Cumulative Layout Shift | Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric. | 1.007 |
| Max Potential First Input Delay | 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. | 670 ms |
| Largest Contentful Paint | Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric | 7.5 s |
| Time to Interactive | 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. | 12.2 s |
| Total Blocking Time | Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric. | 1,260 ms |
| Speed Index | Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric. | 7.8 s |
| Legacy JavaScript | 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
| Est savings of 10 KiB |
| Use efficient cache lifetimes | A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Est savings of 18 KiB |
| First Contentful Paint | First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric. | 2.7 s |
Audit Details
| Audit | Insight | Impact |
|---|---|---|
| Render blocking requests | 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.
| Est savings of 1,620 ms |
| Minimize main-thread work | 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 | 11.0 s |
| Document request latency | Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression. | Est savings of 1,090 ms |
| LCP request discovery | Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading | Open |
| Reduce unused JavaScript | Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| Est savings of 1,539 KiB |
| Forced reflow | 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.
| Open |
| Reduce unused CSS | 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.
| Est savings of 332 KiB |
| Avoid large layout shifts | 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
| 9 layout shifts found |
| Network dependency tree | 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. | Open |
| Reduce JavaScript execution time | 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.
| 6.7 s |
| Reduce initial server response time | 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.
| Root document took 1,190 ms |
| Layout shift culprits | 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. | Open |
| Use efficient cache lifetimes | A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Est savings of 158 KiB |
| Total Blocking Time | Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric. | 4,140 ms |
| Max Potential First Input Delay | 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. | 1,610 ms |
| LCP breakdown | Each subpart has specific improvement strategies. Ideally, most of the LCP time should be spent on loading the resources, not within delays. | Open |
| Speed Index | Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric. | 5.2 s |
| Largest Contentful Paint | Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric | 6.2 s |
| Time to Interactive | 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. | 8.5 s |
| Cumulative Layout Shift | Cumulative Layout Shift measures the movement of visible elements within the viewport. Learn more about the Cumulative Layout Shift metric. | 0.425 |
| First Contentful Paint | First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric. | 2.0 s |
| Image elements do not have explicit `width` and `height` | Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
| Open |
| Avoid enormous network payloads | Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
| Total size was 3,644 KiB |
| Improve image delivery | Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| Est savings of 13 KiB |
| Legacy JavaScript | 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
| Est savings of 7 KiB |
Browser Console Logs
Messages captured from the browser console during the real page test.
info
LegacyDataMixin will be applied to all legacy elements.
Set `_legacyUndefinedCheck: true` on element class to enable.
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
Failed to load resource: net::ERR_NAME_NOT_RESOLVED
error
net::ERR_ABORTED
https://www.youtube.com/ptracking?html5=1&video_id=iI7kyVaNudI&cpn=P1Y74qDH055sGOQv&ei=SnvmafjjILXap-oP07OmiQ4&ptk=youtube_single&oid=iKlKI62iEFRKqVlo4JgD8w&ptchn=xA6osyl5m_BUsycRiscAew&pltype=content
info
Banner not shown: beforeinstallpromptevent.preventDefault() called. The page must call beforeinstallpromptevent.prompt() to show the banner.Chrome UX Report
Real-user experience shares from recent Chrome visits to this website.
Origin: https://www.youtube.com
Mobile 2.2%
Desktop 97.8%
Tablet 0.0%
| Metric | User experience share | 75th percentile |
|---|---|---|
| LCP |
Good 30.2%
Needs improvement 35.3%
Poor 34.5% | 4.91 s |
| INP |
Good 70.2%
Needs improvement 19.3%
Poor 10.5% | 237 ms |
| CLS |
Good 49.4%
Needs improvement 20.5%
Poor 30.1% | 0.31 |
| FCP |
Good 36.6%
Needs improvement 40.4%
Poor 23.0% | 2.89 s |
| TTFB |
Good 84.2%
Needs improvement 9.2%
Poor 6.6% | 529 ms |
Resources by Transfer Size
Largest transferred resources captured during the browser test, sorted from heaviest to lightest.
| Resource | Type | Status | Duration | Transfer size | Decoded size | Blocking |
|---|---|---|---|---|---|---|
| fetch | 200 | 420 ms | 568.3 KB | 568.01 KB | non-blocking | |
www.youtube.com | fetch | 200 | 89 ms | 10.22 KB | 42.63 KB | non-blocking |
www.youtube.com | other | 200 | 9 ms | 5.2 KB | 4.9 KB | non-blocking |
| other | 0 | 73 ms | 5.08 KB | 4.79 KB | non-blocking | |
www.youtube.com | other | 200 | 9 ms | 3.43 KB | 3.14 KB | non-blocking |
www.youtube.com | other | 200 | 77 ms | 446 B | 1.12 KB | non-blocking |
www.youtube.com | xmlhttprequest | 200 | 86 ms | 426 B | 106 B | non-blocking |
| fetch | 204 | 186 ms | 300 B | 0 B | non-blocking | |
| xmlhttprequest | 204 | 73 ms | 300 B | 0 B | non-blocking | |
www.gstatic.com | other | 0 | 11 ms | 0 B | 0 B | non-blocking |
youtube.com | fetch | 0 | 317 ms | 0 B | 0 B | non-blocking |
Get daily monitoring and instant alerts with Observer.
Register Observer to keep testing your website automatically and react faster when something breaks.
Try Observer Discover