Website review, no card needed

annieselke.com logo

annieselke.com website review

Visit site (opens in a new tab)Reviewed 22 October 202636 issues · 83 checks

This review found 36 issues worth fixing on annieselke.com, 18 of them high impact, across 83 checks. The most urgent: reduce unused JavaScript. 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.5 s2.8 sMay 2Oct 173.1 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20263.0 s
May 23, 20263.0 s
May 30, 20263.0 s
Jun 6, 20263.1 s
Jun 13, 20263.2 s
Jun 20, 20263.4 s
Jun 27, 20263.4 s
Jul 4, 20263.3 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.2 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.1 s
Sep 19, 20263.1 s
Sep 26, 20263.1 s
Oct 3, 20263.1 s
Oct 10, 20263.1 s
Oct 17, 20263.1 s
Real-visitor tap response (INP)75th percentile, phones
270 ms199 msMay 2Oct 17228 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026207 ms
May 9, 2026213 ms
May 16, 2026222 ms
May 23, 2026224 ms
May 30, 2026229 ms
Jun 6, 2026236 ms
Jun 13, 2026238 ms
Jun 20, 2026250 ms
Jun 27, 2026262 ms
Jul 4, 2026261 ms
Jul 11, 2026261 ms
Jul 18, 2026259 ms
Jul 25, 2026250 ms
Aug 1, 2026249 ms
Aug 8, 2026244 ms
Aug 15, 2026242 ms
Aug 22, 2026246 ms
Aug 29, 2026253 ms
Sep 5, 2026257 ms
Sep 12, 2026256 ms
Sep 19, 2026255 ms
Sep 26, 2026247 ms
Oct 3, 2026238 ms
Oct 10, 2026228 ms
Oct 17, 2026228 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 annieselke.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. annieselke.com at 0.9 s0.9 s
  2. annieselke.com at 1.7 s1.7 s
  3. annieselke.com at 2.6 s2.6 s
  4. annieselke.com at 3.4 s3.4 s
  5. annieselke.com at 4.3 s4.3 s
  6. annieselke.com at 5.2 s5.2 s
  7. annieselke.com at 6.0 s6.0 s
  8. annieselke.com at 6.9 s6.9 s

Speed

12 to fix41
  • Reduce unused JavaScript

    2.3 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

  • Render-blocking requests

    1.8 s

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

  • Use efficient cache lifetimes

    1.1 s · 668 KiB

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

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 9.2 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, logr-in.com and osano.com and others), adding 2.0 MB and 1.4 s of main-thread time.

  • Improve image delivery

    200 ms · 653 KiB

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

  • Reduce unused CSS

    450 ms · 58 KiB

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

  • Google Tag Manager adds 290 ms

    290 ms

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

  • 2,469 HTML elements

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

  • ZenDesk adds 170 ms

    170 ms

    ZenDesk costs a phone 170 ms of main-thread work and 413 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.

  • Klaviyo adds 129 ms

    129 ms

    Klaviyo costs a phone 129 ms of main-thread work and 365 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.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    76 KiB

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

  • Minify JavaScript

    17 KiB

    17 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 17.6 s

    17.6 s

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

  • Time to Interactive: 31.9 s

    31.9 s

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

  • Speed Index: 10.3 s

    10.3 s

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

  • First Contentful Paint: 4.4 s

    4.4 s

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

  • Total Blocking Time: 647 ms

    647 ms

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

  • 10 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    +8%

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

    1.8 s

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

  • Real-user INP: 155 ms

    155 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 1.5 s

    1.5 s

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

  • Real-user TTFB: 758 ms

    758 ms

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

  • Cumulative Layout Shift: 0.019

    0.019

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

Images and page weight

1 to fix70
  • Page weight: 6.0 MB in 539 requests

    6.0 MB

    Your homepage downloads 6.0 MB in 539 requests on a phone: scripts 3.3 MB (168), other files 1.6 MB (309) and images 854 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 3 images below the first screen load straight away

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

  • About 1.7 g of CO₂ per visit

    1.69 g

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

6 to fixGoogle 8892
  • Images must have alternative text (3 elements)

    Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 4 links without text

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

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

  • Headings skip levels

    Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 47 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: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9283
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Structured data has 1 problem

    Structured data found (Organization) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.annieselke.com/cdn/shop/files/ASC_Logo_Master_Bra…”.

  • No social preview image

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

  • 298 internal links, 10 external

    The homepage links to 298 pages on annieselke.com and 10 external pages.

5 checks passed
  • Meta description: 158 characters

    Your meta description is 158 characters: “Annie Selke's curated collection of rugs, bedding, and décor will elevate your space. Discover the perfect piece to bri…”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Rugs, Bedding, Home Décor, Furniture and More – Annie Selke”.

  • Canonical URL set

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

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.annieselke.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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, description and contact details; sameAs (social profiles) would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix65
  • 2 linked pages are broken

    Your homepage links to https://www.annieselke.com/collections/collab-marie-flanigan-rugs and https://www.annieselke.com/collections/color-blue-rugs, which answer with an error. Visitors hit a dead end and search engines drop them.

  • 2 pages without a meta description

    https://www.annieselke.com/collections/new-rugs and https://www.annieselke.com/collections/color-neutral-rugs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.annieselke.com/pages/rugs, https://www.annieselke.com/collections/bestselling-rugs, https://www.annieselke.com/collections/new-rugs, https://www.annieselke.com/collections/shape-stair-runner-rugs, https://www.annieselke.com/collections/luxury-rugs and https://www.annieselke.com/collections/all-rugs and 4 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 191 found) and read each the way a search engine does.

4 checks passed
  • 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 13 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9671
  • 10 broken images

    10 images failed to load on a phone, for example https://www.annieselke.com/.

  • 17 small tap targets

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

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Default drawer container was not found by id. Specify another one, please!”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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 analytics detected

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

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

    The homepage carries about 751 words of visible text.

4 checks passed
  • 19 calls to action

    The homepage has 19 calls to action, for example “Shop by Color”, “Shop By Material & Technique” and “Learn More”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks and a star rating.

  • Direct contact links

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

Privacy and tracking

  • 4 trackers load before any consent

    4

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

  • 26 cookies set on arrival

    26

    Opening the homepage sets 26 cookies (measured from a US location before any click).

  • 45 other companies contacted

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

1 checks passed
  • Consent tool: Osano

    A consent management tool (Osano) 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 annieselke.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

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 36 issues on annieselke.com, including 18 speed issues, 3 SEO issues and 2 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