Website review, no card needed

annsacks.com logo

annsacks.com website review

Visit site (opens in a new tab)Reviewed 28 October 202633 issues · 83 checks

This review found 33 issues worth fixing on annsacks.com, 13 of them high impact, across 83 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
3.2 s2.2 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.4 s
May 16, 20262.5 s
May 23, 20262.6 s
May 30, 20262.7 s
Jun 6, 20262.7 s
Jun 13, 20262.9 s
Jun 20, 20263.0 s
Jun 27, 20263.1 s
Jul 4, 20263.1 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20263.0 s
Aug 15, 20263.0 s
Aug 22, 20262.9 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.8 s
Sep 19, 20262.8 s
Sep 26, 20262.8 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.6 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
194 ms133 msMay 9Oct 24166 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026171 ms
May 16, 2026163 ms
May 23, 2026170 ms
May 30, 2026172 ms
Jun 6, 2026174 ms
Jun 13, 2026178 ms
Jun 20, 2026171 ms
Jun 27, 2026156 ms
Jul 4, 2026153 ms
Jul 11, 2026143 ms
Jul 18, 2026144 ms
Jul 25, 2026143 ms
Aug 1, 2026140 ms
Aug 8, 2026141 ms
Aug 15, 2026146 ms
Aug 22, 2026153 ms
Aug 29, 2026161 ms
Sep 5, 2026178 ms
Sep 12, 2026183 ms
Sep 19, 2026187 ms
Sep 26, 2026186 ms
Oct 3, 2026179 ms
Oct 10, 2026171 ms
Oct 17, 2026169 ms
Oct 24, 2026166 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 annsacks.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. annsacks.com at 0.6 s0.6 s
  2. annsacks.com at 1.2 s1.2 s
  3. annsacks.com at 1.9 s1.9 s
  4. annsacks.com at 2.5 s2.5 s
  5. annsacks.com at 3.1 s3.1 s
  6. annsacks.com at 3.7 s3.7 s
  7. annsacks.com at 4.4 s4.4 s
  8. annsacks.com at 5.0 s5.0 s

Speed

9 to fix48
  • Use efficient cache lifetimes

    8.3 s · 3.8 MB

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

  • Render-blocking requests

    5.2 s

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

  • Reduce unused CSS

    2.9 s · 654 KiB

    About 654 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.9 s faster on a phone.

  • Reduce unused JavaScript

    2.5 s · 482 KiB

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

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48 (desktop: 44). 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 (Affirm, Optanon and site.com and others), adding 4.8 MB and 209 ms of main-thread time.

  • Adobe Scene7 adds 6 ms

    6 ms

    Adobe Scene7 costs a phone 6 ms of main-thread work and 3.5 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.

  • Main-thread work: 3.1 s

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

  • site.com adds 13 ms

    13 ms

    site.com costs a phone 13 ms of main-thread work and 728 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.

  • Legacy JavaScript

    200 ms · 27 KiB

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

  • Duplicated JavaScript

    200 ms · 3 KiB

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

  • 8 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 3 KiB

    3 KiB could be saved by minifying JavaScript.

  • Font display

    50 ms

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

  • Improve image delivery

    11 KiB

    2 images could be 11 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify CSS

    4 KiB

    4 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 38 ms

    38 ms

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

Core Web Vitals

5 to fix100
  • First Contentful Paint: 9.5 s

    9.5 s

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

  • Largest Contentful Paint: 23.6 s

    23.6 s

    Your largest element takes 23.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cookies may be used on this site and stored on your device …”.

  • Time to Interactive: 23.7 s

    23.7 s

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

  • Speed Index: 11.9 s

    11.9 s

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

  • Total Blocking Time: 323 ms

    323 ms

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

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

    2.4 s

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

  • Real-user INP: 157 ms

    157 ms

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

    1.6 s

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

  • Real-user TTFB: 767 ms

    767 ms

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

  • Cumulative Layout Shift: 0.029

    0.029

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

Images and page weight

1 to fix70
  • Page weight: 7.0 MB in 153 requests

    7.0 MB

    Your homepage downloads 7.0 MB in 153 requests on a phone: media 3.1 MB (1), scripts 2.0 MB (75) and stylesheets 773 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 8 images below the first screen load straight away

    8 images further down the page (211 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    1.98 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 2 images in the HTML carry an alt attribute.

  • 50 automated accessibility rules passed

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

SEO

4 to fixGoogle 9287
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (163 characters)

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

  • No social preview image

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

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 27 internal links, 19 external

    The homepage links to 27 pages on annsacks.com and 19 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “MADE Modern”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Ann Sacks | Luxury Tile & Stone for Inspired Interiors”.

  • Canonical URL set

    The canonical URL is https://annsacks.kohler.com/.

  • 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://annsacks.kohler.com/en/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.

  • No llms.txt

    There is no https://annsacks.kohler.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 (277 words), so crawlers that don't run JavaScript still read it.

Other pages

6 to fix52
  • 1 linked page is broken

    Your homepage links to https://annsacks.kohler.com/content/annsacks/us/en/trade-program, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 2 pages share a title

    https://annsacks.kohler.com/content/annsacks/us/en/find-a-showroom/browse-all-showrooms.html and https://annsacks.kohler.com/find-a-showroom/browse-all-showrooms all use the title “Browse Ann Sacks Tile, Stone & Slab Showrooms - Ann Sacks”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://annsacks.kohler.com/blog has no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages share a meta description

    https://annsacks.kohler.com/content/annsacks/us/en/find-a-showroom/browse-all-showrooms.html and https://annsacks.kohler.com/find-a-showroom/browse-all-showrooms use the same meta description. A description written for each page earns more clicks.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://annsacks.kohler.com/content/annsacks/us/en/find-a-showroom/browse-all-showrooms.html, whose canonical is https://annsacks.kohler.com/find-a-showroom/browse-all-showrooms. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://annsacks.kohler.com/about-us has no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://annsacks.kohler.com/inspiration/by-room and https://annsacks.kohler.com/literature 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 25 found) and read each the way a search engine does.

2 checks passed
  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 14 pages that loaded have a <title>.

Best practices

4 to fixGoogle 7370
  • 5 broken images

    5 images failed to load on a phone, for example https://2tsgm39ucb.execute-api.us-east-1.amazonaws.com/pixel?pid=&event=init.

  • 17 small tap targets

    17 of 26 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use …”.

  • Requests the geolocation permission on page load

    Requests the geolocation permission on page load.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

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

    The homepage carries about 281 words of visible text.

2 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP THE COLLECTION” and “Close newsletter signup modal”.

  • 6 calls to action

    The homepage has 6 calls to action, for example “Request Appointment”, “SHOP THE COLLECTION” and “SHOP OUTDOOR TILE”.

Privacy and tracking

  • 10 trackers load before any consent

    10

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

  • 38 cookies set on arrival

    38

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

  • 65 other companies contacted

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 annsacks.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
Next.js
Hosting
Akamai

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on annsacks.com, including 14 speed issues, 4 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