Website review, no card needed

wickerwoodworks.com logo

wickerwoodworks.com website review

Visit site (opens in a new tab)Reviewed 17 November 202627 issues · 82 checks

This review found 27 issues worth fixing on wickerwoodworks.com, 6 of them high impact, across 82 checks. The most urgent: page weight: 26.2 MB in 246 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.9 s1.3 sMay 30Nov 141.4 s
Show as table
DateReal-visitor load time (LCP)
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.6 s
Jul 11, 20261.6 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.4 s
Aug 29, 20261.4 s
Sep 5, 20261.4 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.7 s
Nov 7, 20261.5 s
Nov 14, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
106 ms78 msMay 30Nov 1495 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202683 ms
Jun 6, 202687 ms
Jun 13, 202688 ms
Jun 20, 202688 ms
Jun 27, 202687 ms
Jul 4, 202687 ms
Jul 11, 202686 ms
Jul 18, 202684 ms
Jul 25, 202682 ms
Aug 1, 202681 ms
Aug 8, 202683 ms
Aug 15, 202685 ms
Aug 22, 202686 ms
Aug 29, 202687 ms
Sep 5, 202687 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202688 ms
Oct 3, 202690 ms
Oct 10, 202690 ms
Oct 17, 202696 ms
Oct 24, 2026102 ms
Oct 31, 2026103 ms
Nov 7, 2026103 ms
Nov 14, 202695 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 wickerwoodworks.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wickerwoodworks.com at 0.9 s0.9 s
  2. wickerwoodworks.com at 1.8 s1.8 s
  3. wickerwoodworks.com at 2.6 s2.6 s
  4. wickerwoodworks.com at 3.5 s3.5 s
  5. wickerwoodworks.com at 4.4 s4.4 s
  6. wickerwoodworks.com at 5.3 s5.3 s
  7. wickerwoodworks.com at 6.2 s6.2 s
  8. wickerwoodworks.com at 7.0 s7.0 s

Speed

9 to fix63
  • Reduce unused JavaScript

    1.0 s · 226 KiB

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

  • Mobile performance score: 63

    63/100

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

  • Improve image delivery

    650 ms · 248 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (boostcommerce.io, Shopify and Klaviyo and others), adding 786 KiB and 612 ms of main-thread time.

  • Render-blocking requests

    500 ms

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

  • Legacy JavaScript

    400 ms · 59 KiB

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

  • Main-thread work: 3.5 s

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

  • boostcommerce.io adds 258 ms

    258 ms

    boostcommerce.io costs a phone 258 ms of main-thread work and 208 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.

  • Shopify adds 182 ms

    182 ms

    Shopify costs a phone 182 ms of main-thread work and 380 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.

  • Use efficient cache lifetimes

    150 ms · 126 KiB

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

  • 3 long tasks on the main thread

    3 long tasks block the main thread while loading, the longest for 224 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).

  • Minify CSS

    36 KiB

    36 KiB could be saved by minifying CSS.

  • Reduce unused CSS

    26 KiB

    About 26 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: 13 ms

    13 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 9.4 s

    9.4 s

    Your largest element takes 9.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The irving turntable station vinyl record storage and recor…”.

  • Speed Index: 8.2 s

    8.2 s

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

  • Time to Interactive: 9.5 s

    9.5 s

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

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

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

    +16%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

8 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: 1.8 s

    1.8 s

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

  • Real-user INP: 96 ms

    96 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 501 ms

    501 ms

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

  • Total Blocking Time: 142 ms

    142 ms

    Scripts block the page for only 142 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

1 to fix70
  • Page weight: 26.2 MB in 246 requests

    26.2 MB

    Your homepage downloads 26.2 MB in 246 requests on a phone: media 24.0 MB (2), scripts 982 KiB (128) and other files 644 KiB (77). Under 2 MB keeps phones on slow connections fast.

  • About 7.4 g of CO₂ per visit

    7.41 g

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

5 to fixGoogle 9594
  • 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 (4 elements)

    All page content should be contained by landmarks: 4 elements on the page fail 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.

  • 2 links without text

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

  • Headings should not be empty (3 elements)

    Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 42 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 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

3 to fixGoogle 8591
  • 3 H1 headlines

    There are 3 <h1> headlines (“”, “” and “”). One clear main headline is easier for people and search engines.

  • 5 links crawlers can't follow

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

  • 83 internal links, 1 external

    The homepage links to 83 pages on wickerwoodworks.com and 1 external page.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Shop handmade solid wood vinyl record storage furniture, record player stands and turntable stations built in Portland,…”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Handmade Vinyl Record Storage Furniture | WickerWoodWorks”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • 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://wickerwoodworks.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

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

3 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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

Other pages

100
  • 15 internal pages checked

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

7 checks passed
  • Linked pages load

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

Best practices

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Thin social proof

    Social proof on the homepage: 17 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

  • About 684 words of copy

    The homepage carries about 684 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: “Shop Now” and “SHOP THE GIFT GUIDE”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “Custom Shop”, “Learn more” and “Shop”.

  • 5 short forms

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Tag Manager, Klaviyo, Meta Pixel, Reddit Pixel and TikTok Pixel (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.

  • 10 cookies set on arrival

    10

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

  • 23 other companies contacted

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

Apps on your store

Your storefront loads 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Judge Me Reviews · Inbox · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Quick Announcement Bar Prod · Product Filter Search · luckyorange.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
React
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
Portland

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 27 issues on wickerwoodworks.com, including 13 speed issues, 3 SEO issues 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