Website review, no card needed

123exteriors.com logo

123exteriors.com website review

Visit site (opens in a new tab)Reviewed 20 October 202628 issues · 78 checks

This review found 28 issues worth fixing on 123exteriors.com, 9 of them high impact, across 78 checks. The most urgent: use efficient cache lifetimes. 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
1.9 s1.3 sMay 2Sep 121.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.6 s
May 30, 20261.5 s
Jun 6, 20261.7 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 11, 20261.4 s
Aug 15, 20261.9 s
Aug 22, 20261.6 s
Aug 29, 20261.5 s
Sep 5, 20261.6 s
Sep 12, 20261.8 s

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 123exteriors.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. 123exteriors.com at 0.4 s0.4 s
  2. 123exteriors.com at 0.9 s0.9 s
  3. 123exteriors.com at 1.3 s1.3 s
  4. 123exteriors.com at 1.7 s1.7 s
  5. 123exteriors.com at 2.1 s2.1 s
  6. 123exteriors.com at 2.6 s2.6 s
  7. 123exteriors.com at 3.0 s3.0 s
  8. 123exteriors.com at 3.4 s3.4 s

Speed

10 to fix43
  • Use efficient cache lifetimes

    1.4 s · 604 KiB

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

  • Mobile performance score: 43

    43/100

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

  • Improve image delivery

    900 ms · 703 KiB

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

  • Render-blocking requests

    900 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Hubspot, Cookiebot and ReachDynamics and others), adding 1.4 MB and 331 ms of main-thread time.

  • Reduce unused CSS

    310 ms · 59 KiB

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

  • 2,593 HTML elements

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

  • Hubspot adds 200 ms

    200 ms

    Hubspot costs a phone 200 ms of main-thread work and 404 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.

  • amcharts.com adds 0 ms

    0 ms

    amcharts.com costs a phone 0 ms of main-thread work and 322 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.

  • nutshell.com adds 0 ms

    0 ms

    nutshell.com costs a phone 0 ms of main-thread work and 310 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 JavaScript

    150 ms · 233 KiB

    About 233 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    150 ms

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

  • 3 long tasks on the main thread

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

  • Minify JavaScript

    42 KiB

    42 KiB could be saved by minifying JavaScript.

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 443 ms of it running JavaScript. That is comfortably low.

  • Server response: 114 ms

    114 ms

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

Core Web Vitals

6 to fix41
  • Largest Contentful Paint: 11.7 s

    11.7 s

    Your largest element takes 11.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “GettyImages-519331904”.

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Cumulative Layout Shift: 0.416

    0.416

    The layout shifts by 0.416 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 7.2 s

    7.2 s

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

  • First Contentful Paint: 3.1 s

    3.1 s

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

  • 1 image without width and height

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

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

    +10%

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

1 checks passed
  • Total Blocking Time: 71 ms

    71 ms

    Scripts block the page for only 71 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 3.1 MB in 112 requests

    3.1 MB

    Your homepage downloads 3.1 MB in 112 requests on a phone: scripts 1.7 MB (51), images 1.2 MB (26) and stylesheets 80 KiB (25). Under 2 MB keeps phones on slow connections fast.

  • 10 images in older formats

    10 images (811 KiB) 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.

  • 12 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.87 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9593
  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 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 (50 elements)

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

  • 22 links without text

    22 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, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 32 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 5 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 9295
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 163 internal links, 5 external

    The homepage links to 163 pages on 123exteriors.com and 5 external pages.

7 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Expert exterior specialists serving multiple states. Free storm damage inspections, quality roofing & siding with insur…”.

  • One H1 headline

    Your main headline reads: “Your Trusted Exterior Experts”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “123 Exteriors - Your Trusted Exterior Experts”.

  • Canonical URL set

    The canonical URL is https://www.123exteriors.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • 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.123exteriors.com/sitemap_index.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,039 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.123exteriors.com/llms.txt (6 KiB, 16 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 68 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 13 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 13 pages that loaded have a <title>.

Best practices

1 to fixGoogle 10093
  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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.

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

    The homepage carries about 581 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: “Instant Quote”.

  • 11 calls to action

    The homepage has 11 calls to action, for example “Instant Quote”, “Contact Us” and “Get Started Today”.

  • 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: 49 testimonial or review blocks, 1 customer or partner logo, a star rating and 7 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • 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

  • 12 other companies contacted

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

2 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 123exteriors.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

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on 123exteriors.com, including 16 speed issues, 2 SEO issues and 1 conversion gap. 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