Website review, no card needed

crossville.com logo

crossville.com website review

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

This review found 36 issues worth fixing on crossville.com, 13 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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.4 s3.7 sMay 30Nov 144.1 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20264.2 s
Jun 6, 20264.2 s
Jun 13, 20264.2 s
Jun 20, 20264.2 s
Jun 27, 20264.1 s
Jul 4, 20264.0 s
Jul 11, 20264.0 s
Jul 18, 20263.9 s
Jul 25, 20263.8 s
Aug 1, 20264.0 s
Aug 8, 20264.0 s
Aug 15, 20264.1 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20264.1 s
Sep 12, 20264.0 s
Sep 19, 20264.0 s
Sep 26, 20264.1 s
Oct 3, 20264.1 s
Oct 10, 20264.1 s
Oct 17, 20264.1 s
Oct 24, 20264.2 s
Oct 31, 20264.3 s
Nov 7, 20264.3 s
Nov 14, 20264.1 s
Real-visitor tap response (INP)75th percentile, phones
352 ms90 msMay 30Nov 14121 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026306 ms
Jun 6, 2026240 ms
Jun 13, 2026236 ms
Jun 20, 2026291 ms
Jun 27, 2026244 ms
Jul 4, 2026322 ms
Jul 11, 2026288 ms
Jul 18, 2026139 ms
Jul 25, 2026125 ms
Aug 1, 2026128 ms
Aug 8, 2026135 ms
Aug 15, 2026142 ms
Aug 22, 2026146 ms
Aug 29, 2026129 ms
Sep 5, 2026126 ms
Sep 12, 2026121 ms
Sep 19, 2026121 ms
Sep 26, 2026126 ms
Oct 3, 2026128 ms
Oct 10, 2026126 ms
Oct 17, 2026128 ms
Oct 24, 2026120 ms
Oct 31, 2026123 ms
Nov 7, 2026128 ms
Nov 14, 2026121 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 crossville.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix64
  • Use efficient cache lifetimes

    3.4 s · 732 KiB

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

  • Reduce unused JavaScript

    2.6 s · 496 KiB

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

  • Render-blocking requests

    1.3 s

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

  • Improve image delivery

    300 ms · 9.3 MB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Hubspot and Clarity and others), adding 11.9 MB and 711 ms of main-thread time.

  • Amazon Web Services adds 0 ms

    0 ms

    Amazon Web Services costs a phone 0 ms of main-thread work and 10.7 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.

  • Mobile performance score: 64

    64/100

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

  • Google Tag Manager adds 399 ms

    399 ms

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

  • Font display

    350 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

  • 2,734 HTML elements

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

  • Hubspot adds 176 ms

    176 ms

    Hubspot costs a phone 176 ms of main-thread work and 313 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.

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    49 KiB

    About 49 KiB of CSS is downloaded but never applied on this page.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • Minify CSS

    6 KiB

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

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 3 ms

    3 ms

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

Core Web Vitals

6 to fix100
  • 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.

  • Largest Contentful Paint: 24.1 s

    24.1 s

    Your largest element takes 24.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “AHF uses cookies and similar technologies to collect and st…”.

  • Time to Interactive: 27.2 s

    27.2 s

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

  • Speed Index: 11.0 s

    11.0 s

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

  • Real-user TTFB: 1.5 s

    1.5 s

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

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

8 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 104 ms

    104 ms

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

    1.7 s

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

  • Tap response (INP) got 54% faster for real visitors

    -54%

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

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

  • Total Blocking Time: 122 ms

    122 ms

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

5 to fix14
  • Page weight: 12.3 MB in 86 requests

    12.3 MB

    Your homepage downloads 12.3 MB in 86 requests on a phone: images 10.7 MB (36), scripts 1.3 MB (25) and fonts 209 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 9 images over 500 KB

    9 images weigh 8.6 MB together. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    1.6 MB

    3 images are downloaded at several times the size a phone draws them, for example df1c0b07-0c16-4e75-b408-6e18f5c4a305.jpg at 2,000 px wide, shown at 358 px. Resized copies would save about 1.6 MB.

  • 22 images in older formats

    22 images (10.2 MB) 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.

  • An image on the first screen is lazy-loaded

    Healthcare_Slate_Alaska_L2523_L2548.jpg 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).

  • About 3.5 g of CO₂ per visit

    3.50 g

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

Accessibility

5 to fixGoogle 9394
  • 3 text elements with low contrast

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

  • 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 (2 elements)

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

  • 16 links without text

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

  • 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 h1 → h3), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 35 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 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9293
  • 2 H1 headlines

    There are 2 <h1> headlines (“Bring beauty to spaces that work hard” and “Bring beauty to spaces that work hard”). One clear main headline is easier for people and search engines.

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

  • 152 internal links, 18 external

    The homepage links to 152 pages on crossville.com and 18 external pages.

7 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “Explore porcelain, glass, and stone tile for residential and commercial spaces. Durable, waterproof solutions for indoo…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Porcelain Tile Solutions for Home and Business | Crossville”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage 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.crossville.com/sitemap_index.xml.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

2 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 (1,043 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 2 pages without a meta description

    https://www.crossville.com/contact/sales-representatives and https://www.crossville.com/visual/glass have no meta description, so Google writes the search snippet from whatever text it finds.

  • 11 pages without an H1

    https://www.crossville.com/application/indoor, https://www.crossville.com/application/outdoor, https://www.crossville.com/application/pool, https://www.crossville.com/application/resort, https://www.crossville.com/application/tile-over-tile and https://www.crossville.com/application/wall and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 9 pages slow to respond

    https://www.crossville.com/application/indoor, https://www.crossville.com/application/outdoor, https://www.crossville.com/application/pool, https://www.crossville.com/application/tile-over-tile, https://www.crossville.com/application/wall and https://www.crossville.com/visual/glass and 3 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 54 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 10084
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=17536641&tm=gtm002&Ver=2&mid=3524dea2-77b0-4e35-98c8-849fe83a48ea&bo=1&sid=2d1551f0e4c811f199e627f260c38b3b&vid=2d159740e4c811f1b0a4d165de3c2d10&vids=1&msclkid=N&pi=91.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    50 of 56 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

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

  • A 10-field form

    Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

  • 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 1,088 words of copy

    The homepage carries about 1,088 words of visible text.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Contact Us”, “Sign Up Today” and “Contact”.

  • Analytics in place

    Analytics detected: Google Tag Manager and HubSpot.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Tag Manager, HubSpot, Microsoft Ads and Microsoft Clarity (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies, 7 of them by other companies (measured from a US location before any click).

  • 22 other companies contacted

    Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: Cookiebot

    A consent management tool (Cookiebot) loads with the page.

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Tag Manager
Hosting
AWS

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 crossville.com, including 17 speed issues, 2 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