Website review, no card needed

absolutepets.com logo

absolutepets.com website review

Visit site (opens in a new tab)Reviewed 28 October 202664 issues · 100 checks

This review found 64 issues worth fixing on absolutepets.com, 28 of them high impact, across 100 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.4 s2.0 sMay 9Oct 242.9 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.2 s
May 16, 20262.2 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.7 s
Jul 4, 20262.8 s
Jul 11, 20263.0 s
Jul 18, 20262.9 s
Jul 25, 20262.9 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.0 s
Sep 5, 20263.1 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.1 s
Oct 3, 20263.0 s
Oct 10, 20262.9 s
Oct 17, 20262.9 s
Oct 24, 20262.9 s
Real-visitor tap response (INP)75th percentile, phones
146 ms118 msMay 9Oct 24136 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026131 ms
May 16, 2026128 ms
May 23, 2026132 ms
May 30, 2026138 ms
Jun 6, 2026141 ms
Jun 13, 2026143 ms
Jun 20, 2026121 ms
Jun 27, 2026128 ms
Jul 4, 2026129 ms
Jul 11, 2026128 ms
Jul 18, 2026129 ms
Jul 25, 2026125 ms
Aug 1, 2026127 ms
Aug 8, 2026132 ms
Aug 15, 2026135 ms
Aug 22, 2026140 ms
Aug 29, 2026136 ms
Sep 5, 2026136 ms
Sep 12, 2026135 ms
Sep 19, 2026137 ms
Sep 26, 2026136 ms
Oct 3, 2026135 ms
Oct 10, 2026136 ms
Oct 17, 2026136 ms
Oct 24, 2026136 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 absolutepets.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. absolutepets.com at 1.9 s1.9 s
  2. absolutepets.com at 3.8 s3.8 s
  3. absolutepets.com at 5.6 s5.6 s
  4. absolutepets.com at 7.5 s7.5 s
  5. absolutepets.com at 9.4 s9.4 s
  6. absolutepets.com at 11.3 s11.3 s
  7. absolutepets.com at 13.2 s13.2 s
  8. absolutepets.com at 15.1 s15.1 s

Speed

15 to fix18
  • Use efficient cache lifetimes

    4.8 s · 10.4 MB

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

  • Improve image delivery

    2.5 s · 1.5 MB

    24 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.5 s faster on a phone.

  • Font display

    3.0 s

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

  • Reduce unused JavaScript

    1.9 s · 722 KiB

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

  • Render-blocking requests

    2.5 s

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

  • Document request latency

    1.1 s

    The HTML itself could arrive about 1.1 s sooner: redirects, a slow server response or missing compression delay everything after it.

  • Reduce initial server response time

    1.1 s

    Reduce initial server response time. Google estimates savings of 1.1 s on a phone.

  • Mobile performance score: 18

    18/100

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

  • 9 long tasks on the main thread

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

  • Reduce unused CSS

    750 ms · 165 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 814 KiB and 703 ms of main-thread time.

  • Google Tag Manager adds 316 ms

    316 ms

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

  • Main-thread work: 3.2 s

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

  • Google CDN adds 213 ms

    213 ms

    Google CDN costs a phone 213 ms of main-thread work and 384 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.

  • Server response: 1.2 s

    1.2 s

    Your server takes 1.2 s to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Legacy JavaScript

    100 ms · 29 KiB

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

  • Minify CSS

    13 KiB

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

Core Web Vitals

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

  • Time to Interactive: 40.3 s

    40.3 s

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

  • Speed Index: 13.5 s

    13.5 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Cumulative Layout Shift: 0.328

    0.328

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

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

    0.14

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

  • Largest content (LCP) got 34% slower for real visitors

    +34%

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

  • Real-user FCP: 2.1 s

    2.1 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 32 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

1 checks passed
  • Real-user INP: 130 ms

    130 ms

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

Images and page weight

4 to fix33
  • Page weight: 11.4 MB in 88 requests

    11.4 MB

    Your homepage downloads 11.4 MB in 88 requests on a phone: scripts 5.2 MB (15), images 4.0 MB (51) and fonts 1.7 MB (9). Under 2 MB keeps phones on slow connections fast.

  • 10 images far larger than shown

    885 KiB

    10 images are downloaded at several times the size a phone draws them, for example acana-free-2kg-web-banners-oct-2026-home-page.jpg at 1,173 px wide, shown at 370 px. Resized copies would save about 885 KiB.

  • 28 images in older formats

    28 images (3.9 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.

  • 11 images below the first screen load straight away

    11 images further down the page (1.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.2 g of CO₂ per visit

    3.24 g

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

Accessibility

17 to fixGoogle 5877
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 10 text elements with low contrast

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

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • <html> element must have a lang attribute (1 element)

    <html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.

  • Form elements should have a visible label (1 element)

    Form elements should have a visible label: 1 element on the page fails this check, rated serious by axe-core.

  • 2 images without alt text

    2 images have no alt text, which hurts accessibility and image search.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 21 links without text

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

  • 2 form fields without a label

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings should not be empty (4 elements)

    Headings should not be empty: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

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

SEO

5 to fixGoogle 7772
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • No H1 headline

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

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links with vague text

    2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

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

  • 10 internal links, 1 external

    The homepage links to 10 pages on absolutepets.com and 1 external page.

4 checks passed
  • Title: 62 characters

    Your title is a healthy 62 characters: “Buy Dog Food, Cat Food and Pet Products Online | Absolute Pets”.

  • Canonical URL set

    The canonical URL is https://www.absolutepets.com/home.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://absolutepets.com/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    19%

    A phone browser shows 376 words, but the HTML your server sends has only 70. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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://absolutepets.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.

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

Other pages

3 to fix83
  • 2 pages share a title

    / and https://absolutepets.com/home all use the title “Buy Dog Food, Cat Food and Pet Products Online | Absolute Pets”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://absolutepets.com/home, https://absolutepets.com/pet-stores, https://absolutepets.com/pet-spas, https://absolutepets.com/contact-us, https://absolutepets.com/blog/category/articles and https://absolutepets.com/blog/category/community-update have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages without an H1

    https://absolutepets.com/home, https://absolutepets.com/pet-stores, https://absolutepets.com/pet-spas, https://absolutepets.com/contact-us, https://absolutepets.com/blog/category/articles and https://absolutepets.com/blog/category/community-update have no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages with very little text

    https://absolutepets.com/home, https://absolutepets.com/pet-stores, https://absolutepets.com/pet-spas, https://absolutepets.com/contact-us, https://absolutepets.com/blog/category/articles and https://absolutepets.com/blog/category/community-update 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.

  • 6 internal pages checked

    We fetched 6 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 6 pages we checked loaded without an error.

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 6 pages that loaded have a <title>.

Best practices

3 to fixGoogle 8183
  • Scrolls sideways on phones

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

  • 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 “Access to XMLHttpRequest at 'https://www.absolutepets.com/bootstrap/3.3.7/css/bootstrap.min.css' from origin 'https://a…”.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

    52 of 54 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix92
  • 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 376 words of copy

    The homepage carries about 376 words of visible text.

5 checks passed
  • Clear next step on the first screen

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

  • 3 calls to action

    The homepage has 3 calls to action, for example “Login / Register”, “Shop Online” and “Contact Us”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and 2 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads 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.

  • 8 cookies set on arrival

    8

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 absolutepets.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
Analytics
Google Analytics
Hosting
Azure

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 64 issues on absolutepets.com, including 28 speed issues, 5 SEO issues and 1 conversion gap. 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