Website review, no card needed

hansons.com logo

hansons.com website review

Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 92 checks

This review found 40 issues worth fixing on hansons.com, 18 of them high impact, across 92 checks. The most urgent: improve image delivery. 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
5.4 s3.0 sMay 9Oct 245.1 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.6 s
May 30, 20264.2 s
Jun 6, 20264.6 s
Jun 13, 20264.9 s
Jun 20, 20264.9 s
Jun 27, 20264.6 s
Jul 4, 20264.5 s
Jul 11, 20264.3 s
Jul 18, 20264.2 s
Jul 25, 20264.0 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20263.9 s
Aug 22, 20263.8 s
Aug 29, 20263.4 s
Sep 5, 20263.3 s
Sep 12, 20263.5 s
Sep 19, 20263.7 s
Sep 26, 20264.3 s
Oct 3, 20264.9 s
Oct 10, 20265.0 s
Oct 17, 20265.1 s
Oct 24, 20265.1 s
Real-visitor tap response (INP)75th percentile, phones
194 ms135 msMay 9Oct 24178 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026144 ms
May 16, 2026145 ms
May 23, 2026144 ms
May 30, 2026153 ms
Jun 6, 2026154 ms
Jun 13, 2026155 ms
Jun 20, 2026158 ms
Jun 27, 2026153 ms
Jul 4, 2026150 ms
Jul 11, 2026145 ms
Jul 18, 2026146 ms
Jul 25, 2026142 ms
Aug 1, 2026147 ms
Aug 8, 2026155 ms
Aug 15, 2026153 ms
Aug 22, 2026158 ms
Aug 29, 2026154 ms
Sep 5, 2026153 ms
Sep 12, 2026161 ms
Sep 19, 2026164 ms
Sep 26, 2026172 ms
Oct 3, 2026187 ms
Oct 10, 2026186 ms
Oct 17, 2026181 ms
Oct 24, 2026178 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 hansons.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. hansons.com at 0.5 s0.5 s
  2. hansons.com at 1.1 s1.1 s
  3. hansons.com at 1.6 s1.6 s
  4. hansons.com at 2.1 s2.1 s
  5. hansons.com at 2.7 s2.7 s
  6. hansons.com at 3.2 s3.2 s
  7. hansons.com at 3.7 s3.7 s
  8. hansons.com at 4.2 s4.2 s

Speed

13 to fix36
  • Improve image delivery

    5.5 s · 1.3 MB

    11 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.5 s faster on a phone.

  • Reduce unused JavaScript

    4.2 s · 1.0 MB

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

  • Render-blocking requests

    4.9 s

    22 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.9 s.

  • Use efficient cache lifetimes

    3.3 s · 764 KiB

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

  • Mobile performance score: 36

    36/100

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

  • Main-thread work: 5.0 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, audioeye.com and Facebook and others), adding 2.4 MB and 2.1 s of main-thread time.

  • Google Tag Manager adds 867 ms

    867 ms

    Google Tag Manager costs a phone 867 ms of main-thread work and 1.0 MB 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.

  • audioeye.com adds 635 ms

    635 ms

    audioeye.com costs a phone 635 ms of main-thread work and 297 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

    450 ms · 78 KiB

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

  • 17 long tasks on the main thread

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

  • Google Maps adds 143 ms

    143 ms

    Google Maps costs a phone 143 ms of main-thread work and 392 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.

  • embedsocial.com adds 54 ms

    54 ms

    embedsocial.com costs a phone 54 ms of main-thread work and 301 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.

  • Legacy JavaScript

    150 ms · 47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Minify JavaScript

    150 ms · 35 KiB

    35 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Phones get a much slower page than desktops

    Desktop scores 61 but mobile only 36. A gap that wide usually means heavy scripts and images that hit phones hardest.

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

1 checks passed
  • Server response: 4 ms

    4 ms

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

Core Web Vitals

12 to fix67
  • Fails Core Web Vitals for real visitors

    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.

  • Real-user LCP: 11.9 s

    11.9 s

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

  • First Contentful Paint: 9.9 s

    9.9 s

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

  • Largest Contentful Paint: 25.1 s

    25.1 s

    Your largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HANSONS sale — 50% off installation plus an extra $500 off.…”.

  • Time to Interactive: 28.0 s

    28.0 s

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

  • Speed Index: 13.8 s

    13.8 s

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

  • Total Blocking Time: 802 ms

    802 ms

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

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

    +24%

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

  • Largest content (LCP) got 54% slower for real visitors

    +54%

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

  • Real-user FCP: 2.7 s

    2.7 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 7 images without width and height

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

3 checks passed
  • Real-user INP: 182 ms

    182 ms

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

  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

3 to fix45
  • Page weight: 4.9 MB in 220 requests

    4.9 MB

    Your homepage downloads 4.9 MB in 220 requests on a phone: scripts 2.6 MB (101), images 1.7 MB (47) and fonts 316 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    fall-warehouse-sale.png weighs 1.1 MB. On a phone connection a single image that size takes seconds.

  • 7 images in older formats

    7 images (1.4 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.

  • About 1.4 g of CO₂ per visit

    1.38 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

7 to fixGoogle 8891
  • 2 text elements with low contrast

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

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 6 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 30 images in the HTML carry an alt attribute.

  • 43 automated accessibility rules passed

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

SEO

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

    Your title is 68 characters, so Google will cut it off around 60: “HANSONS Home Improvement | Windows, Roofing, Siding, Gutters & Baths”.

  • 1 link with vague text

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

  • 107 internal links, 14 external

    The homepage links to 107 pages on hansons.com and 14 external pages.

7 checks passed
  • Meta description: 156 characters

    Your meta description is 156 characters: “Protecting homes across Michigan, Ohio, Indiana, Iowa, Nebraska & South Dakota for 35+ years. Windows, roofing, siding,…”.

  • One H1 headline

    Your main headline reads: “Fall Savings!”.

  • Canonical URL set

    The canonical URL is https://hansons.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://hansons.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 8878
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=4034539&Ver=2&mid=f72a6da6-ed41-4966-9d23-4e329456d032&bo=1&sid=b6033590d26311f1bdb1d3b59c5e9c45&vid=b6038b00d26311f1a8b48f56c37fd482&vids=1&msclkid=N&pi=918639831&lg=.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “InvalidValueError: not an instance of HTMLInputElement”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • About 1,310 words of copy

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

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL US 24/7” and “CONTACT US”.

  • 10 calls to action

    The homepage has 10 calls to action, for example “CALL US 24/7”, “Contact Us” and “Request Service”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 5 customer or partner logos, a star rating, 4 trust badges and “more than 300,000 customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

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, Klaviyo and Meta Pixel 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.

  • 16 cookies set on arrival

    16

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

  • 47 other companies contacted

    Loading the homepage contacts 47 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 hansons.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fastly

Company

Employees
127

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 40 issues on hansons.com, including 25 speed issues and 2 SEO issues. 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