Website review, no card needed

woodfloorstore.ie logo

woodfloorstore.ie website review

Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 85 checks

This review found 34 issues worth fixing on woodfloorstore.ie, 12 of them high impact, across 85 checks. The most urgent: trust Pilot adds 2.1 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
2.1 s922 msMay 16Oct 311.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.6 s
May 23, 20261.4 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.4 s
Aug 29, 20261.6 s
Sep 5, 20261.8 s
Sep 12, 20262.0 s
Sep 19, 20262.0 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.9 s
Oct 24, 20261.9 s
Oct 31, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
244 ms95 msMay 16Oct 31221 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026132 ms
May 23, 2026127 ms
May 30, 2026120 ms
Jun 6, 2026119 ms
Jun 13, 2026116 ms
Jun 20, 2026113 ms
Jun 27, 2026112 ms
Jul 4, 2026112 ms
Jul 11, 2026113 ms
Jul 18, 2026120 ms
Jul 25, 2026128 ms
Aug 1, 2026138 ms
Aug 8, 2026153 ms
Aug 15, 2026172 ms
Aug 22, 2026182 ms
Aug 29, 2026194 ms
Sep 5, 2026203 ms
Sep 12, 2026205 ms
Sep 19, 2026213 ms
Sep 26, 2026223 ms
Oct 3, 2026227 ms
Oct 10, 2026225 ms
Oct 17, 2026227 ms
Oct 24, 2026218 ms
Oct 31, 2026221 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 woodfloorstore.ie (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. woodfloorstore.ie at 1.1 s1.1 s
  2. woodfloorstore.ie at 2.2 s2.2 s
  3. woodfloorstore.ie at 3.2 s3.2 s
  4. woodfloorstore.ie at 4.3 s4.3 s
  5. woodfloorstore.ie at 5.4 s5.4 s
  6. woodfloorstore.ie at 6.5 s6.5 s
  7. woodfloorstore.ie at 7.6 s7.6 s
  8. woodfloorstore.ie at 8.6 s8.6 s

Speed

12 to fix48
  • Trust Pilot adds 2.1 s

    2.1 s

    Trust Pilot costs a phone 2.1 s of main-thread work and 4.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 48

    48/100

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

  • Main-thread work: 9.7 s

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

  • 6,891 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Trust Pilot, elfsightcdn.com and Google Tag Manager and others), adding 5.6 MB and 3.4 s of main-thread time.

  • Improve image delivery

    950 ms · 950 KiB

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

  • Use efficient cache lifetimes

    1.9 MB

    166 files are served with short cache lifetimes, so returning visitors download them again (1.9 MB).

  • Render-blocking requests

    900 ms

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

  • elfsightcdn.com adds 547 ms

    547 ms

    elfsightcdn.com costs a phone 547 ms of main-thread work and 471 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 JavaScript

    526 KiB

    About 526 KiB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 412 ms

    412 ms

    Google Tag Manager costs a phone 412 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.

  • 11 long tasks on the main thread

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

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

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

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

  • Time to Interactive: 40.4 s

    40.4 s

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

  • Largest Contentful Paint: 7.5 s

    7.5 s

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

  • Total Blocking Time: 936 ms

    936 ms

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

  • Speed Index: 7.0 s

    7.0 s

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

  • Real-user INP: 226 ms

    226 ms

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

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

    +69%

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

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

    +20%

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

6 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 CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (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: 338 ms

    338 ms

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

  • First Contentful Paint: 1.4 s

    1.4 s

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

  • Cumulative Layout Shift: 0.022

    0.022

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

Images and page weight

2 to fix60
  • Page weight: 8.9 MB in 845 requests

    8.9 MB

    Your homepage downloads 8.9 MB in 845 requests on a phone: scripts 5.0 MB (236), images 2.0 MB (49) and other files 1.1 MB (382). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    55 KiB

    1 image is downloaded at several times the size a phone draws it, for example gorgias_guy_left.png at 1,024 px wide, shown at 65 px. Resized copies would save about 55 KiB.

  • 6 images in older formats

    6 images (291 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 2.5 g of CO₂ per visit

    2.53 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9794
  • 8 text elements with low contrast

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

  • 1 tap target too small

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

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

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (27 elements).

2 checks passed
  • Every image has alt text

    All 169 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

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

SEO

2 to fixGoogle 9292
  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 365 internal links, 86 external

    The homepage links to 365 pages on woodfloorstore.ie and 86 external pages.

6 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “Quality Flooring with Wholesale Prices | 100% Irish ✔ Online Samples ✔ Nationwide Delivery ✔ Shop Now ➔”.

  • Title: 58 characters

    Your title is a healthy 58 characters: “Wood Floor Store: Ireland's Leading Wood Flooring Supplier”.

  • Canonical URL set

    The canonical URL is https://woodfloorstore.ie/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebSite and WholesaleStore.

  • 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://woodfloorstore.ie/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 (2,656 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

2 to fix90
  • 3 pages without a meta description

    https://woodfloorstore.ie/pages/store-locator, https://woodfloorstore.ie/collections/laminate-straight-planks and https://woodfloorstore.ie/collections/laminate-long-planks have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://woodfloorstore.ie/pages/store-locator 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 142 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.

  • 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

1 to fixGoogle 9693
  • 2 JavaScript errors while loading

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

2 checks passed
  • Tap targets are thumb-sized

    98 of 102 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 616 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop now!” and “Shop Sale”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Shop Sale”, “LAMINATE SHOP →” and “SPC SHOP →”.

  • 4 short forms

    4 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 72 testimonial or review blocks and 4 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

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.

  • 18 cookies set on arrival

    18

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

  • 43 other companies contacted

    Loading the homepage contacts 43 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 woodfloorstore.ie, 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

Ta Labels Badges · Tinyseo Ai Seo Speed · Gorgias Live Chat Helpdesk · Klaviyo Email Marketing Sms · Countdown Timer · chimpstatic.com · trustpilot.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 | Microsoft Clarity
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on woodfloorstore.ie, including 20 speed issues, 2 SEO 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