asurion.com website review

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

Your mobile performance score is 35 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

A phone's processor spends 6.8 s on main-thread work while loading, 4.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google Tag Manager, Dynatrace and Facebook and others), adding 1.8 MB and 1.9 s of main-thread time.

20 files are served with short cache lifetimes, so returning visitors download them again (707 KiB).

Google Tag Manager costs a phone 780 ms of main-thread work and 709 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

20 long tasks block the main thread while loading, the longest for 622 ms. During a long task the page ignores taps.

Dynatrace costs a phone 301 ms of main-thread work and 80 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

4 images could be 98 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 30 KiB of CSS is downloaded but never applied on this page.

Polyfills for old browsers add 21 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 15.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “An image of an Asurion Expert visiting a family on their po…”.

The page becomes fully interactive after 47.1 s. Good is under 3.8 s.

Visually, the page fills in at 13.6 s (Speed Index). Good is under 3.4 s.

Scripts block taps and scrolling for 1.6 s in total while the page loads. Good is under 200 ms.

Real visitors wait 217 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 155 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Real visitors wait 850 ms for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.7 s on a phone. Good is under 1.8 s.

3 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 2.9 s to 3.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.3 MB in 241 requests on a phone: scripts 4.2 MB (61), images 2.1 MB (66) and other files 1.4 MB (101). Under 2 MB keeps phones on slow connections fast.

16 images (1.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

Start_a_claim.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

3 images further down the page (96 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.35 g of CO₂e: 282.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Some lists contain elements other than list items, which screen readers announce wrongly.

Elements with visible text labels do not have matching accessible names. (2 elements).

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 83 pages on asurion.com and 11 external pages.

There is no /llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

/repairs/tech and /home/repair/fix-it all use the title “All Your Technology Repaired By Pros | Asurion Tech Repair”. Search engines can't tell which page to show for a search, so each competes with the others.

/repairs/tech and /home/repair/fix-it use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example /home/repair/fix-it, whose canonical is /repairs/tech. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/claims and /phone-insurance/app-center have no <h1> headline, so visitors and search engines get no clear main topic.

/fix-it-appliance, /phone-insurance, /repairs/tech/smartphones/screen-repair and /sustainability/recycle took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 43 found) and read each the way a search engine does.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

Large scripts ship without source maps.

4 links go through two or more redirects, for example https://www.asurion.com/cricket/.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

asurion.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

asurion.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 465 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 2 cookies (measured from a US location before any click).

Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.