Website review, no card needed

decks-docks.com logo

decks-docks.com website review

Visit site (opens in a new tab)Reviewed 22 October 202631 issues · 85 checks

This review found 31 issues worth fixing on decks-docks.com, 10 of them high impact, across 85 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

Real-visitor load time (LCP)75th percentile, phones
1.6 s1.3 sMay 2Oct 171.5 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.4 s
May 9, 20261.4 s
May 16, 20261.4 s
May 23, 20261.4 s
May 30, 20261.4 s
Jun 6, 20261.4 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.5 s
Jul 4, 20261.5 s
Jul 11, 20261.5 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.5 s
Sep 5, 20261.5 s
Sep 12, 20261.5 s
Sep 19, 20261.5 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.5 s
Oct 17, 20261.5 s
Real-visitor tap response (INP)75th percentile, phones
170 ms143 msMay 2Oct 17163 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026148 ms
May 9, 2026146 ms
May 16, 2026146 ms
May 23, 2026147 ms
May 30, 2026151 ms
Jun 6, 2026154 ms
Jun 13, 2026154 ms
Jun 20, 2026155 ms
Jun 27, 2026154 ms
Jul 4, 2026154 ms
Jul 11, 2026154 ms
Jul 18, 2026154 ms
Jul 25, 2026154 ms
Aug 1, 2026158 ms
Aug 8, 2026154 ms
Aug 15, 2026154 ms
Aug 22, 2026154 ms
Aug 29, 2026154 ms
Sep 5, 2026157 ms
Sep 12, 2026163 ms
Sep 19, 2026162 ms
Sep 26, 2026165 ms
Oct 3, 2026167 ms
Oct 10, 2026167 ms
Oct 17, 2026163 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 decks-docks.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix56
  • Render-blocking requests

    3.3 s

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

  • Reduce unused JavaScript

    1.9 s · 408 KiB

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

  • Mobile performance score: 56

    56/100

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

  • Use efficient cache lifetimes

    750 ms · 223 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and leadferno.com and others), adding 1.1 MB and 858 ms of main-thread time.

  • Improve image delivery

    857 KiB

    11 images could be 857 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 459 ms

    459 ms

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

  • Facebook adds 251 ms

    251 ms

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

  • leadferno.com adds 146 ms

    146 ms

    leadferno.com costs a phone 146 ms of main-thread work and 313 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

    280 ms · 21 KiB

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    150 ms · 12 KiB

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

  • 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 91 but mobile only 56. 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.

2 checks passed
  • Main-thread work: 2.0 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 14.9 s

    14.9 s

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

  • Time to Interactive: 16.7 s

    16.7 s

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

  • First Contentful Paint: 3.5 s

    3.5 s

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

  • Speed Index: 6.0 s

    6.0 s

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

  • Total Blocking Time: 335 ms

    335 ms

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

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

    +12%

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

  • Largest content (LCP) held steady for real visitors

    +9%

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

7 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: 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 INP: 136 ms

    136 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 752 ms

    752 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix63
  • Page weight: 28.7 MB in 93 requests

    28.7 MB

    Your homepage downloads 28.7 MB in 93 requests on a phone: media 25.6 MB (2), images 1.6 MB (25) and scripts 1.2 MB (32). Under 2 MB keeps phones on slow connections fast.

  • 12 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (207 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.

  • About 8.1 g of CO₂ per visit

    8.13 g

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

8 to fixGoogle 8290
  • 47 text elements with low contrast

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

  • Positive tabindex

    2 elements have a tabindex above 0, which scrambles the keyboard order.

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

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

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails 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.

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

  • Zoom is disabled

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

  • 13 links without text

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

  • Headings skip levels

    Headings skip levels (h1 → h5, h3 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 41 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: 41 passed and 9 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

1 to fixGoogle 9298
  • 6 links with vague text

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

  • 116 internal links, 8 external

    The homepage links to 116 pages on decks-docks.com and 8 external pages.

8 checks passed
  • Meta description: 90 characters

    Your meta description is 90 characters: “Decks & Docks is your source for premium decking, dock, and marine construction materials.”.

  • One H1 headline

    Your main headline reads: “Decks & Docks. We deliver no matter what.”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “The Top Marine Construction Supplier | Decks & Docks”.

  • Canonical URL set

    The canonical URL is https://www.decks-docks.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 and points crawlers to your sitemap.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.decks-docks.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 (913 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.decks-docks.com/llms.txt (2 KiB, 19 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 84 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 9687
  • 8 small tap targets

    8 of 13 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 “Failed to load resource: net::ERR_FAILED”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • Thin social proof

    Social proof on the homepage: 4 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

    The homepage carries about 775 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Join Our Team”, “Contact” and “Learn More”.

  • 3 short forms

    3 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 6 cookies set on arrival

    6

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

  • 18 other companies contacted

    Loading the homepage contacts 18 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 decks-docks.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 | Microsoft Clarity

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 31 issues on decks-docks.com, including 14 speed issues, 1 SEO issue 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