Website review, no card needed

stikwood.com logo

stikwood.com website review

Visit site (opens in a new tab)Reviewed 20 November 202636 issues · 86 checks

This review found 36 issues worth fixing on stikwood.com, 12 of them high impact, across 86 checks. The most urgent: main-thread work: 15.2 s. 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
4.8 s1.1 sMay 30Nov 143.4 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20264.2 s
Jul 4, 20264.3 s
Jul 11, 20264.4 s
Jul 18, 20264.3 s
Jul 25, 20264.1 s
Aug 1, 20264.0 s
Aug 8, 20263.9 s
Aug 15, 20263.8 s
Aug 22, 20263.6 s
Aug 29, 20263.6 s
Sep 5, 20263.7 s
Sep 12, 20263.7 s
Sep 19, 20263.8 s
Sep 26, 20263.9 s
Oct 3, 20263.9 s
Oct 10, 20264.0 s
Oct 17, 20264.0 s
Oct 24, 20263.7 s
Oct 31, 20263.4 s
Nov 7, 20263.1 s
Nov 14, 20263.4 s
Real-visitor tap response (INP)75th percentile, phones
285 ms74 msMay 30Nov 14194 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026102 ms
Jun 6, 2026102 ms
Jun 13, 202698 ms
Jun 20, 202698 ms
Jun 27, 2026159 ms
Jul 4, 2026206 ms
Jul 11, 2026217 ms
Jul 18, 2026219 ms
Jul 25, 2026211 ms
Aug 1, 2026203 ms
Aug 8, 2026198 ms
Aug 15, 2026195 ms
Aug 22, 2026210 ms
Aug 29, 2026211 ms
Sep 5, 2026218 ms
Sep 12, 2026222 ms
Sep 19, 2026227 ms
Sep 26, 2026241 ms
Oct 3, 2026255 ms
Oct 10, 2026261 ms
Oct 17, 2026250 ms
Oct 24, 2026227 ms
Oct 31, 2026205 ms
Nov 7, 2026187 ms
Nov 14, 2026194 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 stikwood.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. stikwood.com at 3.7 s3.7 s
  2. stikwood.com at 7.5 s7.5 s
  3. stikwood.com at 11.2 s11.2 s
  4. stikwood.com at 15.0 s15.0 s
  5. stikwood.com at 18.7 s18.7 s
  6. stikwood.com at 22.5 s22.5 s
  7. stikwood.com at 26.2 s26.2 s
  8. stikwood.com at 29.9 s29.9 s

Speed

15 to fix15
  • Main-thread work: 15.2 s

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

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 15

    15/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (YouTube, Google Tag Manager and PayPal and others), adding 2.7 MB and 2.6 s of main-thread time.

  • Reduce unused JavaScript

    190 ms · 1.2 MB

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

  • Improve image delivery

    150 ms · 968 KiB

    7 images could be 968 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.

  • YouTube adds 786 ms

    786 ms

    YouTube costs a phone 786 ms of main-thread work and 1,003 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

    480 ms · 170 KiB

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

  • Google Tag Manager adds 521 ms

    521 ms

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

    558 KiB

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

  • PayPal adds 420 ms

    420 ms

    PayPal costs a phone 420 ms of main-thread work and 393 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.

  • Klaviyo adds 382 ms

    382 ms

    Klaviyo costs a phone 382 ms of main-thread work and 401 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 339 ms

    339 ms

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

  • 20 long tasks on the main thread

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

  • 1,781 HTML elements

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

  • Legacy JavaScript

    55 KiB

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

  • Minify CSS

    30 ms · 13 KiB

    13 KiB could be saved by minifying CSS.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 27 ms

    27 ms

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

Core Web Vitals

7 to fix100
  • Largest Contentful Paint: 12.8 s

    12.8 s

    Your largest element takes 12.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “slatwood”.

  • Speed Index: 31.9 s

    31.9 s

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

  • Time to Interactive: 26.3 s

    26.3 s

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

  • Cumulative Layout Shift: 0.914

    0.914

    The layout shifts by 0.914 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 1.4 s

    1.4 s

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

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

    +87%

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

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

    +100%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 3.4 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: 141 ms

    141 ms

    Real visitors wait 141 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.3 s

    1.3 s

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

  • Real-user TTFB: 464 ms

    464 ms

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

  • First Contentful Paint: 1.3 s

    1.3 s

    The first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.

Images and page weight

4 to fix36
  • Page weight: 8.6 MB in 498 requests

    8.6 MB

    Your homepage downloads 8.6 MB in 498 requests on a phone: images 3.6 MB (61), scripts 2.7 MB (96) and other files 1.5 MB (308). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    a4bae744-0bdb-4539-9a47-fb5bbc530b70.png weighs 945 KiB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    Woodwol_Ember_ASH2_Dimensional_Reclaimed_Mosaic_Wood_Wall_Ti is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • 1 image in older formats

    1 image (945 KiB) is 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 2.4 g of CO₂ per visit

    2.43 g

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

4 to fixGoogle 8996
  • 5 text elements with low contrast

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • Links look like plain text

    2 links inside paragraphs rely on colour alone to stand out.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 105 images in the HTML carry an alt attribute.

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

SEO

Google 100100
  • 141 internal links, 7 external

    The homepage links to 141 pages on stikwood.com and 7 external pages.

8 checks passed
  • Meta description: 111 characters

    Your meta description is 111 characters: “Stikwood: Reclaimed & sustainable wood for accent walls & ceilings. Browse collections & find your perfect fit.”.

  • One H1 headline

    Your main headline reads: “Stikwood — Peel & Stick Real Wood Walls & Ceilings”.

  • Title: 50 characters

    Your title is a healthy 50 characters: “Rethink Walls & Ceilings with Real Wood | Stikwood”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: ImageObject, Organization 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.stikwood.com/sitemap.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 (897 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.stikwood.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.stikwood.com/collections/woodwol-mosaic-wood-wall-ceiling-tiles is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without an H1

    https://www.stikwood.com/collections/slatwood-acoustic-slat-wall-and-ceiling-panels 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 85 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 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 a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    86 of 94 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix83
  • 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 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 562 words of copy

    The homepage carries about 562 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP SLATWOOD” and “SHOP STIKWOOD”.

  • 17 calls to action

    The homepage has 17 calls to action, for example “shop all”, “shop samples” and “Shop Slatwood”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 31 cookies set on arrival

    31

    Opening the homepage sets 31 cookies, 1 of them by other companies (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.

  • 41 other companies contacted

    Loading the homepage contacts 41 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 stikwood.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Yotpo Product Reviews · Klaviyo Email Marketing Sms · hubapi.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
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Cloudflare

Company

Headquarters
Sacramento

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 36 issues on stikwood.com, including 22 speed 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