Website review, no card needed

divinefloor.com logo

divinefloor.com website review

Visit site (opens in a new tab)Reviewed 23 October 202632 issues · 83 checks

This review found 32 issues worth fixing on divinefloor.com, 6 of them high impact, across 83 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.2 s910 msMay 2Oct 171.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.1 s
May 9, 20261.1 s
May 16, 20261.1 s
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.1 s
Jul 11, 20261.1 s
Jul 18, 20261.1 s
Jul 25, 20261.1 s
Aug 1, 20261.2 s
Aug 8, 20261.1 s
Aug 15, 20261.0 s
Aug 22, 2026992 ms
Aug 29, 20261.0 s
Sep 5, 2026998 ms
Sep 12, 20261.0 s
Sep 19, 2026991 ms
Sep 26, 2026946 ms
Oct 3, 2026985 ms
Oct 10, 2026999 ms
Oct 17, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
89 ms60 msMay 2Oct 1775 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202665 ms
May 9, 202663 ms
May 16, 202666 ms
May 23, 202671 ms
May 30, 202675 ms
Jun 6, 202679 ms
Jun 13, 202679 ms
Jun 20, 202681 ms
Jun 27, 202681 ms
Jul 4, 202681 ms
Jul 11, 202685 ms
Jul 18, 202679 ms
Jul 25, 202686 ms
Aug 1, 202679 ms
Aug 8, 202678 ms
Aug 15, 202672 ms
Aug 22, 202670 ms
Aug 29, 202670 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202666 ms
Sep 26, 202664 ms
Oct 3, 202666 ms
Oct 10, 202667 ms
Oct 17, 202675 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 divinefloor.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix70
  • Render-blocking requests

    1.1 s

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

  • Improve image delivery

    500 ms · 656 KiB

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

  • Reduce unused JavaScript

    600 ms · 491 KiB

    About 491 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • Mobile performance score: 70

    70/100

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

  • Use efficient cache lifetimes

    543 KiB

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

  • Reduce unused CSS

    300 ms · 47 KiB

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

  • Legacy JavaScript

    300 ms · 37 KiB

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

  • 2,199 HTML elements

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

  • Google Maps adds 133 ms

    133 ms

    Google Maps costs a phone 133 ms of main-thread work and 447 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 45 ms

    45 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Maps, Shopify and cloudfront.net and others), adding 960 KiB and 286 ms of main-thread time.

  • Duplicated JavaScript

    150 ms · 8 KiB

    8 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 150 ms faster on a phone.

  • 2 long tasks on the main thread

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

  • 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: 1.9 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 8.6 s

    8.6 s

    Your largest element takes 8.6 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: 13.2 s

    13.2 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 1 image without width and height

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

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

    +11%

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

  • Largest content (LCP) held steady for real visitors

    +1%

    Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.1 s to 1.1 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.2 s

    1.2 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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: 0.8 s

    0.8 s

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

  • Real-user TTFB: 485 ms

    485 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

  • Total Blocking Time: 62 ms

    62 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.9 MB in 252 requests

    3.9 MB

    Your homepage downloads 3.9 MB in 252 requests on a phone: images 1.4 MB (16), scripts 1.1 MB (68) and other files 981 KiB (150). Under 2 MB keeps phones on slow connections fast.

  • About 1.1 g of CO₂ per visit

    1.10 g

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

4 to fixGoogle 9294
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

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

  • 1 form field without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3 and h3 → 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.

  • 39 automated accessibility rules passed

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

SEO

4 to fixGoogle 8587
  • 2 H1 headlines

    There are 2 <h1> headlines (“Studio JBC Artisan tile” and “SURFACELIFT”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://divinefloor.com/search?q={search_term_string}")”.

  • 3 links with vague text

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 48 internal links, 15 external

    The homepage links to 48 pages on divinefloor.com and 15 external pages.

6 checks passed
  • Meta description: 160 characters

    Your meta description is 160 characters: “Divine Flooring provides natural wood and luxury vinyl flooring collections and sells through distribution channels in …”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Flooring Collections Company Canada | USA | Divine Flooring”.

  • Canonical URL set

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

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

  • llms.txt published

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

Other pages

1 to fix95
  • 8 pages without a meta description

    https://divinefloor.com/pages/two-girls-a-hammer-chicago-waldorf, https://divinefloor.com/pages/genevieve-freed-waterloo-house, https://divinefloor.com/pages/averton-full-house-lottery-home, https://divinefloor.com/pages/oro-trattoria, https://divinefloor.com/pages/sarah-gallop-design-upward-construction and https://divinefloor.com/pages/saunders-architect-y-house and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages with very little text

    https://divinefloor.com/pages/d-zine, https://divinefloor.com/pages/store-locator, https://divinefloor.com/pages/two-girls-a-hammer-chicago-waldorf, https://divinefloor.com/pages/genevieve-freed-waterloo-house, https://divinefloor.com/pages/averton-full-house-lottery-home and https://divinefloor.com/pages/oro-trattoria and 6 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 15 internal pages checked

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

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

  • 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
  • 11 small tap targets

    11 of 29 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

4 to fix63
  • 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.

  • 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 analytics detected

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

  • Only about 227 words

    The homepage has only about 227 words of visible text; thin pages give Google and first-time buyers little to go on.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “SHOP NOW”, “JOIN OUR TEAM” and “Sign Up”.

  • 5 short forms

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

  • Direct contact links

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

  • 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
  • 3 trackers load before any consent

    3

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

  • 21 other companies contacted

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

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on divinefloor.com, including 15 speed issues, 4 SEO issues and 4 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