Website review, no card needed

levis4floors.com logo

levis4floors.com website review

Visit site (opens in a new tab)Reviewed 8 November 202639 issues · 90 checks

This review found 39 issues worth fixing on levis4floors.com, 12 of them high impact, across 90 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
2.3 s1.4 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.2 s
May 23, 20262.2 s
May 30, 20261.9 s
Jun 6, 20261.8 s
Jun 13, 20261.6 s
Jun 20, 20261.7 s
Jun 27, 20261.8 s
Jul 4, 20261.5 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.6 s
Aug 1, 20261.8 s
Aug 8, 20261.8 s
Aug 15, 20261.7 s
Aug 22, 20261.8 s
Aug 29, 20261.7 s
Sep 5, 20261.8 s
Sep 12, 20261.9 s
Sep 19, 20261.8 s
Sep 26, 20262.1 s
Oct 3, 20261.9 s
Oct 10, 20261.9 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
151 ms88 msMay 16Oct 31131 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026107 ms
May 23, 2026110 ms
May 30, 2026105 ms
Jun 6, 2026101 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 2026102 ms
Jul 4, 2026119 ms
Jul 11, 2026121 ms
Jul 18, 2026113 ms
Jul 25, 2026112 ms
Aug 1, 2026104 ms
Aug 8, 2026108 ms
Aug 15, 2026112 ms
Aug 22, 2026127 ms
Aug 29, 2026129 ms
Sep 5, 2026124 ms
Sep 12, 2026129 ms
Sep 19, 2026121 ms
Sep 26, 2026119 ms
Oct 3, 2026128 ms
Oct 10, 2026127 ms
Oct 17, 2026133 ms
Oct 24, 2026144 ms
Oct 31, 2026131 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 levis4floors.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. levis4floors.com at 0.4 s0.4 s
  2. levis4floors.com at 0.8 s0.8 s
  3. levis4floors.com at 1.2 s1.2 s
  4. levis4floors.com at 1.6 s1.6 s
  5. levis4floors.com at 2.0 s2.0 s
  6. levis4floors.com at 2.4 s2.4 s
  7. levis4floors.com at 2.8 s2.8 s
  8. levis4floors.com at 3.2 s3.2 s

Speed

9 to fix56
  • Render-blocking requests

    1.1 s

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

  • Reduce unused JavaScript

    600 ms · 858 KiB

    About 858 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and bc-solutions.net and others), adding 1.9 MB and 1.2 s of main-thread time.

  • Mobile performance score: 56

    56/100

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

  • Google Tag Manager adds 731 ms

    731 ms

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

  • Improve image delivery

    500 ms · 58 KiB

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

  • Use efficient cache lifetimes

    150 ms · 379 KiB

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

  • Reduce unused CSS

    300 ms · 72 KiB

    About 72 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.

  • Main-thread work: 3.5 s

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

  • 10 long tasks on the main thread

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

  • Legacy JavaScript

    51 KiB

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

  • Minify CSS

    36 KiB

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

1 checks passed
  • Server response: 6 ms

    6 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 25.5 s

    25.5 s

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

  • Largest Contentful Paint: 9.2 s

    9.2 s

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

  • Speed Index: 6.3 s

    6.3 s

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

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

    +27%

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

  • Total Blocking Time: 527 ms

    527 ms

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

  • 1 image without width and height

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

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

    1.5 s

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

  • Real-user INP: 118 ms

    118 ms

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

  • Real-user CLS: 0.10

    0.10

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 573 ms

    573 ms

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

  • Largest content (LCP) got 15% faster for real visitors

    -15%

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

  • First Contentful Paint: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix70
  • Page weight: 4.1 MB in 217 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 217 requests on a phone: scripts 2.9 MB (83), other files 720 KiB (111) and images 183 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • About 1.2 g of CO₂ per visit

    1.16 g

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

11 to fixGoogle 7385
  • Images must have alternative text (1 element)

    Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

  • 9 text elements with low contrast

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

  • 7 tap targets too small

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

  • Hidden but focusable

    4 elements hidden from screen readers can still receive keyboard focus.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Malformed lists

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

  • Orphan list items

    Some list items are not inside a list.

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Alternative text of images should not be repeated as text (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

1 checks passed
  • 48 automated accessibility rules passed

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

SEO

3 to fixGoogle 9283
  • Title is short (12 characters)

    Your title is only 12 characters: “Levis4Floors”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

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

  • Meta description is long (236 characters)

    Your meta description is 236 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 149 internal links, 7 external

    The homepage links to 149 pages on levis4floors.com and 7 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: 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.levis4floors.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.levis4floors.com/pages/premier-flooring-center and https://www.levis4floors.com/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.

  • 12 pages without an H1

    https://www.levis4floors.com/pages/premier-flooring-center, https://www.levis4floors.com/pages/columbus-carpet, https://www.levis4floors.com/pages/carpet-how-its-made, https://www.levis4floors.com/pages/carpet-before-you-buy, https://www.levis4floors.com/pages/carpet-maintenance and https://www.levis4floors.com/pages/columbus-carpet-installation and 6 others have 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 65 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

2 to fixGoogle 7391
  • 9 third-party cookies

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

  • 1 JavaScript error while loading

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

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    13 of 15 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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.

  • Thin social proof

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

  • A 17-field form

    Your longest form asks for 17 fields (16 required). Every extra field lowers completion.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

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

  • About 430 words of copy

    The homepage carries about 430 words of visible text.

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL US”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Shop Flooring Chevron down icon”, “Carpet Before You Buy” and “Laminate Before You Buy”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Meta Pixel.

  • Direct contact links

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

  • Phone number on the homepage

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

  • 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 Amazon Ads, Google Ads, Google Analytics, Google Tag Manager and Meta 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.

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

  • 32 other companies contacted

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

Apps your storefront loads

Cart Metadata Sync · Google Reviews · Pagefly Ai Page Builder · Product Filter Search

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
Analytics
Google Tag Manager
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

Company

Employees
180
Headquarters
Columbus

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on levis4floors.com, including 15 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