Website review, no card needed

alpinepainting.com logo

alpinepainting.com website review

Visit site (opens in a new tab)Reviewed 21 October 202634 issues · 84 checks

This review found 34 issues worth fixing on alpinepainting.com, 9 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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

Full-page screenshot of alpinepainting.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix53
  • Render-blocking requests

    2.0 s

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

  • Main-thread work: 4.2 s

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

  • Reduce unused JavaScript

    300 ms · 1.3 MB

    About 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google CDN and Hubspot and others), adding 3.1 MB and 1.3 s of main-thread time.

  • Mobile performance score: 53

    53/100

    Your mobile performance score is 53 (desktop: 80). Pages that score under 90 lose visitors before the first paint.

  • Use efficient cache lifetimes

    613 KiB

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

  • Google Tag Manager adds 478 ms

    478 ms

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

  • Google CDN adds 393 ms

    393 ms

    Google CDN costs a phone 393 ms of main-thread work and 1.5 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.

  • Hubspot adds 279 ms

    279 ms

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

  • 1,572 HTML elements

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

  • Improve image delivery

    150 ms · 204 KiB

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

  • Minify CSS

    150 ms · 8 KiB

    8 KiB could be saved by minifying CSS.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    24 KiB

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

  • Phones get a much slower page than desktops

    Desktop scores 80 but mobile only 53. 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: 13 ms

    13 ms

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

Core Web Vitals

5 to fix56
  • Time to Interactive: 26.0 s

    26.0 s

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

  • Largest Contentful Paint: 8.1 s

    8.1 s

    Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Total Blocking Time: 403 ms

    403 ms

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

  • 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
  • Cumulative Layout Shift: 0.017

    0.017

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

Images and page weight

1 to fix70
  • Page weight: 6.4 MB in 157 requests

    6.4 MB

    Your homepage downloads 6.4 MB in 157 requests on a phone: scripts 3.0 MB (34), images 2.3 MB (83) and other files 721 KiB (22). Under 2 MB keeps phones on slow connections fast.

  • About 1.8 g of CO₂ per visit

    1.81 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 8488
  • 9 text elements with low contrast

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

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

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

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

    All page content should be contained by landmarks: 40 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • 1 link without text

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

2 checks passed
  • Every image has alt text

    All 211 images in the HTML carry an alt attribute.

  • 24 automated accessibility rules passed

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

SEO

4 to fixGoogle 9281
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 2 problems

    Structured data found (BreadcrumbList, Organization and WebPage) but with 2 problems, for example “Organization: missing name”.

  • No social preview image

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

  • 5 links with vague text

    5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 232 internal links, 6 external

    The homepage links to 232 pages on alpinepainting.com and 6 external pages.

5 checks passed
  • Meta description: 154 characters

    Your meta description is 154 characters: “Alpine Painting and Sandblasting Contractors have over 50+ years of excellence in commercial, industrial, in-house shop…”.

  • Title: 64 characters

    Your title is a healthy 64 characters: “Commercial and Industrial Painting Contractors | Alpine Painting”.

  • Canonical URL set

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

  • 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.alpinepainting.com/sitemaps-1-sitemap.xml.

AI search readiness

1 to fix88
  • Organization data is thin (0 of 6 facts)

    Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles), 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.

  • No llms.txt

    There is no https://alpinepainting.com/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.

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

  • Text is in the HTML

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

Other pages

2 to fix88
  • 3 pages share a title

    https://alpinepainting.com/portfolio/commercial, https://alpinepainting.com/portfolio/shop and https://alpinepainting.com/portfolio/flooring all use the title “Alpine Painting”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 8 pages without a meta description

    https://alpinepainting.com/portfolio/commercial, https://alpinepainting.com/portfolio/industrial, https://alpinepainting.com/portfolio/shop, https://alpinepainting.com/flooring, https://alpinepainting.com/portfolio/flooring and https://alpinepainting.com/portfolio/welding and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages with very little text

    https://alpinepainting.com/portfolio/shop, https://alpinepainting.com/portfolio/flooring and https://alpinepainting.com/portfolio/welding have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 1 page slow to respond

    https://alpinepainting.com/flooring took over 3 s to send its HTML from our server.

  • 15 internal pages checked

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

5 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 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

3 to fixGoogle 9285
  • 8 small tap targets

    8 of 31 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “LT.JS: The lt.min.js file cannot run because client 15982 is not permitted to call Lotame's servers.”.

  • 14 distorted images

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

1 checks passed
  • 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 map or directions link

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

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

    The homepage carries about 1,441 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: “SHOP SERVICES”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Request Estimate”, “Contact” and “Shop”.

  • 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: 31 testimonial or review blocks and 102 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, HubSpot and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 6 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

  • 5 trackers load before any consent

    5

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

  • 11 cookies set on arrival

    11

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

  • 34 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 alpinepainting.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
Webflow
Framework
jQuery
Analytics
Google 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 34 issues on alpinepainting.com, including 15 speed issues, 4 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