Website review, no card needed

autotexwipers.com logo

autotexwipers.com website review

Visit site (opens in a new tab)Reviewed 6 November 202630 issues · 82 checks

This review found 30 issues worth fixing on autotexwipers.com, 4 of them high impact, across 82 checks. The most urgent: main-thread work: 4.1 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
2.3 s1.0 sJun 6Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.1 s
Jun 13, 20261.8 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.8 s
Jul 11, 20261.8 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.5 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.6 s
Sep 12, 20261.5 s
Sep 19, 20261.4 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.3 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
108 ms85 msSep 5Oct 3188 ms
Show as table
DateReal-visitor tap response (INP)
Sep 5, 2026105 ms
Sep 19, 2026104 ms
Sep 26, 202695 ms
Oct 17, 202695 ms
Oct 31, 202688 ms

Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.

One score from every part of this review. How it works

Full-page screenshot of autotexwipers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. autotexwipers.com at 0.7 s0.7 s
  2. autotexwipers.com at 1.5 s1.5 s
  3. autotexwipers.com at 2.2 s2.2 s
  4. autotexwipers.com at 3.0 s3.0 s
  5. autotexwipers.com at 3.7 s3.7 s
  6. autotexwipers.com at 4.4 s4.4 s
  7. autotexwipers.com at 5.2 s5.2 s
  8. autotexwipers.com at 5.9 s5.9 s

Speed

9 to fix72
  • Main-thread work: 4.1 s

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

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    350 ms · 507 KiB

    19 images could be 507 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused JavaScript

    611 KiB

    About 611 KiB of JavaScript is downloaded but never used on this page.

  • 7 third-party services on the page

    7 third-party services load with your homepage (Hubspot, Shopify and Klaviyo and others), adding 1.1 MB and 456 ms of main-thread time.

  • Render-blocking requests

    400 ms

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

  • 1,587 HTML elements

    The page has 1,587 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Shopify adds 97 ms

    97 ms

    Shopify costs a phone 97 ms of main-thread work and 408 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.

  • retellai.com adds 47 ms

    47 ms

    retellai.com costs a phone 47 ms of main-thread work and 468 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.

  • Reduce unused CSS

    150 ms · 30 KiB

    About 30 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • 17 long tasks on the main thread

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

  • Use efficient cache lifetimes

    104 KiB

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

  • Legacy JavaScript

    44 KiB

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

  • Chained critical requests

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

  • Forced reflow

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

  • Minify JavaScript

    5 KiB

    5 KiB could be saved by minifying JavaScript.

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 23 ms

    23 ms

    Your server sent the HTML in 23 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Time to Interactive: 12.1 s

    12.1 s

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

  • Largest Contentful Paint: 4.1 s

    4.1 s

    Your largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Wiper Express.”.

  • Total Blocking Time: 491 ms

    491 ms

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

  • Speed Index: 3.8 s

    3.8 s

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

10 checks passed
  • Passes Core Web Vitals for real visitors

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

  • Real-user LCP: 1.4 s

    1.4 s

    Real visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 88 ms

    88 ms

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

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 574 ms

    574 ms

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

  • Tap response (INP) got 12% faster for real visitors

    -12%

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

  • Largest content (LCP) got 35% faster for real visitors

    -35%

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

  • First Contentful Paint: 1.6 s

    1.6 s

    The first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

2 to fix81
  • Page weight: 3.2 MB in 178 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 178 requests on a phone: scripts 1.2 MB (62), images 1.0 MB (31) and other files 749 KiB (66). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    071f3646-a754-4f38-885f-65453342e3e0_2e4844d2-fd8b-4a33-983a 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).

  • About 0.9 g of CO₂ per visit

    0.92 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 10097
  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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.

  • 9 links without text

    9 visible links have no text or label, so screen readers cannot say where they go.

  • Alternative text of images should not be repeated as text (8 elements)

    Alternative text of images should not be repeated as text: 8 elements on the page fail this check, rated minor by axe-core.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 104 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “WiperExpress | Windshield Wiper Blades, Wiper Motors, and Wiper Arms”.

  • Meta description is long (163 characters)

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

  • 189 internal links, 6 external

    The homepage links to 189 pages on autotexwipers.com and 6 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Wiper Express. Since 1991.”.

  • Canonical URL set

    The canonical URL is https://www.wiperexpress.com/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.wiperexpress.com/sitemap.xml.

AI search readiness

100
4 checks passed
  • AI answer engines may read the site

    Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.

  • Organization data: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,031 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.wiperexpress.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

5 to fix63
  • 1 page without a title

    https://www.wiperexpress.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://www.wiperexpress.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.wiperexpress.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.wiperexpress.com/pages/commercial-accounts, whose canonical is https://www.wiperexpress.com/pages/wholesale. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://www.wiperexpress.com/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

2 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Titles are unique

    Every page we checked has its own title.

Best practices

1 to fixGoogle 9693
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'split')”.

2 checks passed
  • Tap targets are thumb-sized

    23 of 23 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • Local business without LocalBusiness data

    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.

  • Thin social proof

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

  • No analytics detected

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

  • No opening hours

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

  • 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 355 words of copy

    The homepage carries about 355 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “TALK TO A SPECIALIST: 800-528-3048” and “COMMERCIAL PRICING”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Talk to a specialist: 800-528-3048”, “Apply for an Account” and “Talk to Our Team”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage.

  • Direct contact links

    Visitors can reach you directly: 3 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 1 more (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.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 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.

  • 27 other companies contacted

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

Security, domain, email and software versions

The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at autotexwipers.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Forms · Wholesale All In One · hubapi.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Sanford

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on autotexwipers.com, including 13 speed issues, 2 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.

  • 28 research agents read your site, reviews, competitors, communities and public filings
  • Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
  • Competitor intelligence with battlecards for your closest rivals
  • Ideal customer profile, buyer segments and buying-stage funnel
  • Ranked channels, outreach sequences and content angles
  • Live Reddit threads where buyers ask for what you sell, with draft replies
  • Earned media and PR openings
  • At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
  • PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
  • Refresh the playbook later to see what changed

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25