Website review, no card needed

dickslumber.com logo

dickslumber.com website review

Visit site (opens in a new tab)Reviewed 30 October 202649 issues · 92 checks

This review found 49 issues worth fixing on dickslumber.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
2.5 s1.9 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.0 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.1 s
Jul 18, 20262.1 s
Jul 25, 20262.0 s
Aug 1, 20262.1 s
Aug 8, 20262.1 s
Aug 15, 20262.1 s
Aug 22, 20262.1 s
Aug 29, 20262.2 s
Sep 5, 20262.3 s
Sep 12, 20262.3 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.4 s
Oct 10, 20262.4 s
Oct 17, 20262.4 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
80 ms69 msMay 9Oct 2479 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202671 ms
May 16, 202671 ms
May 23, 202671 ms
May 30, 202671 ms
Jun 6, 202670 ms
Jun 13, 202671 ms
Jun 20, 202671 ms
Jun 27, 202671 ms
Jul 4, 202672 ms
Jul 11, 202675 ms
Jul 18, 202678 ms
Jul 25, 202671 ms
Aug 1, 202671 ms
Aug 8, 202671 ms
Aug 15, 202670 ms
Aug 22, 202673 ms
Aug 29, 202674 ms
Sep 5, 202677 ms
Sep 12, 202678 ms
Sep 19, 202677 ms
Sep 26, 202677 ms
Oct 3, 202674 ms
Oct 10, 202672 ms
Oct 17, 202673 ms
Oct 24, 202679 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 dickslumber.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix65
  • Improve image delivery

    1.3 s · 1.1 MB

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

  • Render-blocking requests

    1.9 s

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

  • Reduce unused JavaScript

    1.2 s · 211 KiB

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

  • Reduce unused CSS

    900 ms · 198 KiB

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

  • Mobile performance score: 65

    65/100

    Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 218 ms

    218 ms

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

  • Main-thread work: 2.5 s

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google Fonts and others), adding 546 KiB and 228 ms of main-thread time.

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    10 KiB

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

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

  • Use efficient cache lifetimes

    4 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (4 KiB).

  • Minify JavaScript

    2 KiB

    2 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 45 ms

    45 ms

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

Core Web Vitals

9 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 CLS: 0.44

    0.44

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

  • Largest Contentful Paint: 16.7 s

    16.7 s

    Your largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “DICK'S LUMBER Where The Builders Buy! Knowledgeable Staff, …”.

  • Time to Interactive: 17.0 s

    17.0 s

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

  • Speed Index: 6.8 s

    6.8 s

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.1 s

    1.1 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +7%

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

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

    +16%

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

4 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 82 ms

    82 ms

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

  • Total Blocking Time: 115 ms

    115 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix33
  • 1 image over 500 KB

    Careers_1.png weighs 552 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    508 KiB

    3 images are downloaded at several times the size a phone draws them, for example Careers_1.png at 1,920 px wide, shown at 362 px. Resized copies would save about 508 KiB.

  • Page weight: 3.6 MB in 295 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 295 requests on a phone: images 1.8 MB (25), scripts 970 KiB (223) and fonts 615 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (1.2 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.

  • 7 images below the first screen load straight away

    7 images further down the page (1.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    1.03 g

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

Accessibility

10 to fixGoogle 7787
  • 7 buttons without a name

    7 buttons have no accessible name, so screen readers announce just “button”.

  • 5 tap targets too small

    5 tap targets are too small or too close together to hit reliably with a finger.

  • 4 text elements with low contrast

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

  • 4 links without text

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

  • ARIA role should be appropriate for the element (2 elements)

    ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 22 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

7 to fixGoogle 9270
  • No H1 headline

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

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No XML sitemap

    No XML sitemap at https://dickslumber.com/sitemap.xml, so Google discovers your pages only by following links.

  • No robots.txt

    There is no robots.txt at dickslumber.com/robots.txt, the first file search crawlers ask for.

  • 2 links crawlers can't follow

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

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 100 internal links, 6 external

    The homepage links to 100 pages on dickslumber.com and 6 external pages.

2 checks passed
  • Meta description: 132 characters

    Your meta description is 132 characters: “Find all building supplies for your next project at Dick's Lumber. The largest contractor building supply company in We…”.

  • Title: 47 characters

    Your title is a healthy 47 characters: “Dick's Lumber | Building Supplies & Lumber Yard”.

AI search readiness

1 to fix81
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix86
  • 1 linked page hidden from search

    https://dickslumber.com/contact-our-locations/burnaby is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 2 pages without a meta description

    https://dickslumber.com/services and https://dickslumber.com/contractors have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://dickslumber.com/contact-our-locations and https://dickslumber.com/products.html use the same meta description. A description written for each page earns more clicks.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 60 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

4 to fixGoogle 8570
  • 5 broken images

    5 images failed to load on a phone, for example https://dickslumber.com/pub/media/Group_1403_3x.png.

  • 18 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://dickslumber.com/%7B%7BMEDIA_URL%7D%7Dstyles.css' because its MIME type ('text/html…”.

  • 2 distorted images

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

  • 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 (“Content security policy”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

    The homepage carries about 462 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “LEARN MORE”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “My Quote” and “Learn More”.

  • 2 short forms

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

  • Analytics in place

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

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 15 cookies set on arrival

    15

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

  • 5 other companies contacted

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

Upkeep, stack and company

  • The footer still says © 2020.

Stack

E-commerce
Magento
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 49 issues on dickslumber.com, including 16 speed issues, 7 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