Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

origin-checkcoverage-aws-usw2.apple.com

Check Your Service and Support Coverage - Apple Support

Page Load Speed

1.1 sec in total

First Response

156 ms

Resources Loaded

802 ms

Page Rendered

111 ms

About Website

Welcome to origin-checkcoverage-aws-usw2.apple.com homepage info - get ready to check Origin Check Coverage Awsusw2 Apple best content for United States right away, or after learning these important things about origin-checkcoverage-aws-usw2.apple.com

Check your Apple warranty status. Enter a serial number to review your eligibility for support and extended coverage.

Visit origin-checkcoverage-aws-usw2.apple.com

Key Findings

We analyzed Origin-checkcoverage-aws-usw2.apple.com page load time and found that the first response time was 156 ms and then it took 913 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

origin-checkcoverage-aws-usw2.apple.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

11/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value3,870 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.384

27/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

origin-checkcoverage-aws-usw2.apple.com

156 ms

checkcoverage.apple.com

142 ms

header.js

149 ms

footer.js

149 ms

64 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Origin-checkcoverage-aws-usw2.apple.com, 53% (10 requests) were made to Checkcoverage.apple.com and 26% (5 requests) were made to Apple.com. The less responsive or slowest element that took the longest time to load (156 ms) belongs to the original domain Origin-checkcoverage-aws-usw2.apple.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 68.5 kB (65%)

Content Size

105.4 kB

After Optimization

36.9 kB

In fact, the total size of Origin-checkcoverage-aws-usw2.apple.com main page is 105.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. HTML takes 105.4 kB which makes up the majority of the site volume.

HTML Optimization

-65%

Potential reduce by 68.5 kB

  • Original 105.4 kB
  • After minification 104.3 kB
  • After compression 36.9 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 68.5 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (31%)

Requests Now

13

After Optimization

9

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Origin Check Coverage Awsusw2 Apple. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

origin-checkcoverage-aws-usw2.apple.com accessibility score

98

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

origin-checkcoverage-aws-usw2.apple.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

origin-checkcoverage-aws-usw2.apple.com SEO score

98

Search Engine Optimization Advices

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Origin-checkcoverage-aws-usw2.apple.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Origin-checkcoverage-aws-usw2.apple.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph description is not detected on the main page of Origin Check Coverage Awsusw2 Apple. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: