esrtech.com website review

Not measured in this review.

• Real-user FCP: 1.9 s

  1.9 s

  Real visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.

• Real-user TTFB: 1.2 s

  1.2 s

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

• Tap response (INP) got 15% slower for real visitors

  +15%

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

• Page weight: 8.8 MB

  8.8 MB

  Your homepage downloads 8.8 MB on a phone, 7.1 MB of it images (81%). Under 2 MB keeps phones on slow connections fast.

• About 2.5 g of CO₂ per visit

  2.48 g

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

• 1 button without a name

  1 button has no accessible name, so screen readers announce just “button”.

  Elements (1)

• 79 text elements with low contrast

  79 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  Elements (3)

• 1 tap target too small

  1 tap target is too small or too close together to hit reliably with a finger.

  Elements (1)

• 2 images without alt text

  2 images have no alt text, which hurts accessibility and image search.

  Elements (1)

• All page content should be contained by landmarks (21 elements)

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

  Elements (3)

• 2 form fields without a label

  2 form fields have no label, so screen readers announce an empty box and autofill guesses.

• Headings skip levels

  Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

  View source

• Meta description is long (176 characters)

  Your meta description is 176 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• 888 internal links, 62 external

  The homepage links to 888 pages on esrtech.com and 62 external pages.

• Organization data is thin (3 of 6 facts)

  Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  View source

• No llms.txt

  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.

• 7 pages without an H1

  /collections/ipad-mini-8-cases, /pages/apple-event-iphone-accessories, /pages/be-esrtech-superuser, /pages/specialsalezone, /pages/referral and /collections/protective-cases and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

• 3 pages slow to respond

  /pages/apple-event-iphone-accessories, /pages/be-esrtech-superuser and /pages/specialsalezone took over 3 s to send their HTML from our server.

• 15 internal pages checked

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

• 3 JavaScript errors while loading

  3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Short HSTS lifetime

  HSTS is set, but max-age is 91 days; one year is the recommended minimum.

• No Referrer-Policy

  No Referrer-Policy header, so full URLs can leak to the sites you link to.

• No Permissions-Policy

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

• Deprecated X-XSS-Protection

  X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

• No security.txt

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

• DNSSEC is off

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

• Thin social proof

  Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

• No direct contact details

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

• No risk reducer

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

• About 1,960 words of copy

  The homepage carries about 1,960 words of visible text.

• Email authentication score: 90/100

  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.

• 4 trackers load before any consent

  4

  Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel and Microsoft Clarity (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

• 6 cookies set on arrival

  6

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

• No consent tool detected

  No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

• 22 other companies contacted

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