Website review, no card needed

abbycart.com logo

abbycart.com website review

Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 89 checks

This review found 41 issues worth fixing on abbycart.com, 16 of them high impact, across 89 checks. The most urgent: page weight: 115.6 MB in 344 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
3.4 s2.8 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.2 s
May 9, 20263.3 s
May 16, 20263.3 s
May 23, 20263.3 s
May 30, 20263.2 s
Jun 6, 20263.1 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.0 s
Jul 11, 20263.0 s
Jul 18, 20263.0 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.3 s
Aug 22, 20263.3 s
Aug 29, 20263.3 s
Sep 5, 20263.3 s
Sep 12, 20263.3 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
132 ms91 msMay 2Oct 17121 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202696 ms
May 9, 202696 ms
May 16, 202696 ms
May 23, 202697 ms
May 30, 2026102 ms
Jun 6, 2026101 ms
Jun 13, 2026102 ms
Jun 20, 2026103 ms
Jun 27, 2026102 ms
Jul 4, 2026101 ms
Jul 11, 2026101 ms
Jul 18, 2026103 ms
Jul 25, 2026106 ms
Aug 1, 2026112 ms
Aug 8, 2026119 ms
Aug 15, 2026121 ms
Aug 22, 2026122 ms
Aug 29, 2026126 ms
Sep 5, 2026127 ms
Sep 12, 2026127 ms
Sep 19, 2026123 ms
Sep 26, 2026125 ms
Oct 3, 2026122 ms
Oct 10, 2026121 ms
Oct 17, 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 abbycart.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. abbycart.com at 0.5 s0.5 s
  2. abbycart.com at 1.1 s1.1 s
  3. abbycart.com at 1.6 s1.6 s
  4. abbycart.com at 2.2 s2.2 s
  5. abbycart.com at 2.7 s2.7 s
  6. abbycart.com at 3.3 s3.3 s
  7. abbycart.com at 3.8 s3.8 s
  8. abbycart.com at 4.4 s4.4 s

Speed

8 to fix56
  • Reduce unused JavaScript

    1.8 s · 390 KiB

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

  • 6,673 HTML elements

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

  • Main-thread work: 5.0 s

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

  • Mobile performance score: 56

    56/100

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

  • Use efficient cache lifetimes

    650 ms · 102 KiB

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

  • Reduce unused CSS

    300 ms · 41 KiB

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

  • Improve image delivery

    281 KiB

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

  • Shopify adds 111 ms

    111 ms

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Shopify, Klaviyo and Bing Ads and others), adding 916 KiB and 188 ms of main-thread time.

  • Render-blocking requests

    250 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 250 ms.

  • Legacy JavaScript

    150 ms · 24 KiB

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

  • 10 long tasks on the main thread

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

  • Font display

    50 ms

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

  • 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: 35 ms

    35 ms

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

Core Web Vitals

9 to fix33
  • 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: 13.2 s

    13.2 s

    Your largest element takes 13.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Person using Apple AirTag with iPhone to track location on …”.

  • Time to Interactive: 14.1 s

    14.1 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • First Contentful Paint: 3.6 s

    3.6 s

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

  • Real-user LCP: 2.8 s

    2.8 s

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

  • Real-user CLS: 0.13

    0.13

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

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

    +26%

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

  • Cumulative Layout Shift: 0.106

    0.106

    The layout shifts by 0.106 while loading, so content jumps under the reader's thumb. Good is under 0.1.

5 checks passed
  • Real-user INP: 121 ms

    121 ms

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

  • Real-user FCP: 1.4 s

    1.4 s

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

  • Real-user TTFB: 604 ms

    604 ms

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

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

    -10%

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

  • Total Blocking Time: 116 ms

    116 ms

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

Images and page weight

1 to fix70
  • Page weight: 115.6 MB in 344 requests

    115.6 MB

    Your homepage downloads 115.6 MB in 344 requests on a phone: media 112.4 MB (41), scripts 1.0 MB (136) and other files 817 KiB (131). Under 2 MB keeps phones on slow connections fast.

  • About 32.8 g of CO₂ per visit

    32.75 g

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

10 to fixGoogle 8187
  • Images must have alternative text (2 elements)

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

  • <svg> elements with an img or image role must have alternative text (22 elements)

    <svg> elements with an img or image role must have alternative text: 22 elements on the page fail this check, rated serious by axe-core.

  • 6 text elements with low contrast

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

  • Elements must only use permitted ARIA attributes (2 elements)

    Elements must only use permitted ARIA attributes: 2 elements on the page fail this check, rated serious by axe-core.

  • Malformed lists

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

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 18 form fields without a label

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

  • 5 links without text

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

  • Users should be able to zoom and scale the text up to 500% (1 element)

    Users should be able to zoom and scale the text up to 500%: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h4, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.

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

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

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

SEO

4 to fixGoogle 8581
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Shop Premium AirTag Accessories for Pets, Wallets & More – Abbycart”.

  • 13 H1 headlines

    There are 13 <h1> headlines (“”, “Trendy Ideas to use your Apple AirTag” and “Featured on”). One clear main headline is easier for people and search engines.

  • Meta description is long (235 characters)

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

  • 2 links crawlers can't follow

    2 links have no real href, so search engines can't follow them.

  • 175 internal links, 26 external

    The homepage links to 175 pages on abbycart.com and 26 external pages.

5 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, SiteNavigationElement, 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://abbycart.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 4 pages without a meta description

    https://abbycart.com/collections/all, https://abbycart.com/policies/refund-policy, https://abbycart.com/apps/convertout/home and https://abbycart.com/policies/terms-of-service have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://abbycart.com/apps/parcelpanel and https://abbycart.com/apps/convertout/home 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 68 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

4 to fixGoogle 9269
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=134182256&Ver=2&mid=03ebe419-576e-4318-832f-d886d7fe72ad&bo=1&sid=3bfc16c0cbf911f1a145e71d3f1a80bb&vid=3bfc2aa0cbf911f1a47e4d2ab75e904f&vids=0&msclkid=N&pi=918639831&l.

  • Scrolls sideways on phones

    On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

2 checks passed
  • Tap targets are thumb-sized

    16 of 18 tappable elements near the top are at least 24 px.

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

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

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

4 checks passed
  • 23 calls to action

    The homepage has 23 calls to action, for example “Contact Us”, “Track Your Order” and “Track Order Status”.

  • 14 short forms

    14 short forms (2 fields at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 93 testimonial or review blocks and 14 trust badges.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 9 trackers load before any consent

    9

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 4 mores (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.

  • 21 cookies set on arrival

    21

    Opening the homepage sets 21 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.

  • 34 other companies contacted

    Loading the homepage contacts 34 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 abbycart.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 41 issues on abbycart.com, including 17 speed issues, 4 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