Website review, no card needed

cascadefenceanddeck.com logo

cascadefenceanddeck.com website review

Visit site (opens in a new tab)Reviewed 7 November 202635 issues · 87 checks

This review found 35 issues worth fixing on cascadefenceanddeck.com, 14 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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.8 s1.5 sMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.8 s
May 23, 20261.7 s
May 30, 20261.7 s
Jun 6, 20261.7 s
Jun 13, 20261.7 s
Jun 20, 20261.7 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.6 s
Aug 1, 20261.7 s
Aug 8, 20261.7 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.6 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
171 ms100 msMay 16Oct 31158 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026113 ms
May 23, 2026115 ms
May 30, 2026120 ms
Jun 6, 2026113 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026111 ms
Jul 4, 2026108 ms
Jul 11, 2026111 ms
Jul 18, 2026110 ms
Jul 25, 2026110 ms
Aug 1, 2026112 ms
Aug 8, 2026120 ms
Aug 15, 2026126 ms
Aug 22, 2026128 ms
Aug 29, 2026129 ms
Sep 5, 2026132 ms
Sep 12, 2026132 ms
Sep 19, 2026137 ms
Sep 26, 2026145 ms
Oct 3, 2026151 ms
Oct 10, 2026156 ms
Oct 17, 2026163 ms
Oct 24, 2026163 ms
Oct 31, 2026158 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 cascadefenceanddeck.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. cascadefenceanddeck.com at 0.4 s0.4 s
  2. cascadefenceanddeck.com at 0.8 s0.8 s
  3. cascadefenceanddeck.com at 1.1 s1.1 s
  4. cascadefenceanddeck.com at 1.5 s1.5 s
  5. cascadefenceanddeck.com at 1.9 s1.9 s
  6. cascadefenceanddeck.com at 2.3 s2.3 s
  7. cascadefenceanddeck.com at 2.6 s2.6 s
  8. cascadefenceanddeck.com at 3.0 s3.0 s

Speed

12 to fix24
  • Reduce unused JavaScript

    3.1 s · 818 KiB

    About 818 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.1 s faster on a phone.

  • Use efficient cache lifetimes

    2.5 s · 733 KiB

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

  • Mobile performance score: 24

    24/100

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

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

  • 8 third-party services on the page

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

  • Google Tag Manager adds 852 ms

    852 ms

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

  • Render-blocking requests

    450 ms

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

  • posthog.com adds 373 ms

    373 ms

    posthog.com costs a phone 373 ms of main-thread work and 261 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.

  • 18 long tasks on the main thread

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

  • Facebook adds 264 ms

    264 ms

    Facebook costs a phone 264 ms of main-thread work and 282 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.

  • Hubspot adds 215 ms

    215 ms

    Hubspot costs a phone 215 ms of main-thread work and 484 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,914 HTML elements

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

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

  • Duplicated JavaScript

    150 ms · 19 KiB

    19 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • Font display

    50 ms

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

  • Reduce unused CSS

    18 KiB

    About 18 KiB of CSS is downloaded but never applied on this page.

  • 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: 66 ms

    66 ms

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

Core Web Vitals

10 to fix50
  • 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 CLS: 0.51

    0.51

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

  • Largest Contentful Paint: 18.3 s

    18.3 s

    Your largest element takes 18.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “BUILD IN THE OFF-SEASON, WHILE YOUR SPACE IS UNUSED.”.

  • Time to Interactive: 21.2 s

    21.2 s

    The page becomes fully interactive after 21.2 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.

  • Total Blocking Time: 1.1 s

    1.1 s

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

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

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

    +41%

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

  • Real-user TTFB: 1.4 s

    1.4 s

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

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • Largest content (LCP) held steady for real visitors

    -1%

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

2 checks passed
  • Real-user LCP: 2.2 s

    2.2 s

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

  • Real-user FCP: 1.8 s

    1.8 s

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 119 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 119 requests on a phone: scripts 2.1 MB (48), images 737 KiB (25) and fonts 216 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (37 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.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

2 to fixGoogle 9497
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (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 85 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

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

SEO

3 to fixGoogle 8591
  • 3 H1 headlines

    There are 3 <h1> headlines (“Home Page May 12 2025 Version”, “” and “Your Local Fence, Deck, Patio Cover, Sauna Instal…”). One clear main headline is easier for people and search engines.

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

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

  • 176 internal links, 15 external

    The homepage links to 176 pages on cascadefenceanddeck.com and 15 external pages.

7 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “Customers love Cascade Fence & Deck because we are enjoyably uncomplicated, straight shooting and assured, and fun to w…”.

  • Title: 46 characters

    Your title is a healthy 46 characters: “Cascade Fence and Deck - Design & Installation”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://cascadefenceanddeck.com/sitemap_index.xml.

AI search readiness

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

    Your Organization JSON-LD is missing 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://cascadefenceanddeck.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,777 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 1 page without an H1

    https://cascadefenceanddeck.com/decks/deck-railing 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 53 found) and read each the way a search engine does.

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

  • 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 6976
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187275344&tm=gtm002&Ver=2&mid=aafae4f7-e11a-4aed-ab33-67832f358b6f&bo=1&sid=68adf370da7d11f1bd8aff168fdc9472&vid=68ae1000da7d11f1b9a20f436815cd57&vids=1&msclkid=N&gtm_.

  • 2 small tap targets

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

  • 1 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

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

5 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Buy Steel Posts”, “Buy Material” and “Get a Free Estimate!”.

  • Social proof on the page

    Social proof on the homepage: 33 testimonial or review blocks and 61 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (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.

  • 25 cookies set on arrival

    25

    Opening the homepage sets 25 cookies, 7 of them by other companies (measured from a US location before any click).

  • 33 other companies contacted

    Loading the homepage contacts 33 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 cascadefenceanddeck.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
Cloudflare

Hiring

Hiring
3 open roles
Job board
jazzhr

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 35 issues on cascadefenceanddeck.com, including 22 speed issues, 3 SEO issues and 2 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