Website review, no card needed

apupabove.com logo

apupabove.com website review

Visit site (opens in a new tab)Reviewed 18 November 202637 issues · 84 checks

This review found 37 issues worth fixing on apupabove.com, 14 of them high impact, across 84 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
4.1 s1.3 sMay 30Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.5 s
Jul 18, 20262.5 s
Jul 25, 20263.0 s
Aug 1, 20263.5 s
Aug 8, 20263.7 s
Aug 15, 20263.8 s
Aug 22, 20263.7 s
Aug 29, 20263.2 s
Sep 5, 20262.3 s
Sep 12, 20262.0 s
Sep 19, 20261.9 s
Sep 26, 20261.8 s
Oct 3, 20261.7 s
Oct 10, 20261.7 s
Oct 17, 20261.7 s
Oct 24, 20261.7 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
234 ms124 msMay 30Nov 14144 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026146 ms
Jun 6, 2026153 ms
Jun 13, 2026152 ms
Jun 20, 2026146 ms
Jun 27, 2026143 ms
Jul 4, 2026137 ms
Jul 11, 2026137 ms
Jul 18, 2026139 ms
Jul 25, 2026163 ms
Aug 1, 2026195 ms
Aug 8, 2026213 ms
Aug 15, 2026221 ms
Aug 22, 2026212 ms
Aug 29, 2026178 ms
Sep 5, 2026145 ms
Sep 12, 2026146 ms
Sep 19, 2026146 ms
Sep 26, 2026154 ms
Oct 3, 2026161 ms
Oct 10, 2026162 ms
Oct 17, 2026174 ms
Oct 24, 2026170 ms
Oct 31, 2026170 ms
Nov 7, 2026160 ms
Nov 14, 2026144 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 apupabove.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. apupabove.com at 4.3 s4.3 s
  2. apupabove.com at 8.5 s8.5 s
  3. apupabove.com at 12.8 s12.8 s
  4. apupabove.com at 17.1 s17.1 s
  5. apupabove.com at 21.4 s21.4 s
  6. apupabove.com at 25.6 s25.6 s
  7. apupabove.com at 29.9 s29.9 s
  8. apupabove.com at 34.2 s34.2 s

Speed

13 to fix60
  • Reduce unused JavaScript

    1.7 s · 719 KiB

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

  • Use efficient cache lifetimes

    1.0 s · 552 KiB

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

  • Main-thread work: 6.0 s

    A phone's processor spends 6.0 s on main-thread work while loading, 3.1 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 (alia-prod.com, heatmap.com and Google Tag Manager and others), adding 2.1 MB and 1.5 s of main-thread time.

  • Mobile performance score: 60

    60/100

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

  • alia-prod.com adds 620 ms

    620 ms

    alia-prod.com costs a phone 620 ms of main-thread work and 332 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.

  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    100 ms · 360 KiB

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

  • heatmap.com adds 251 ms

    251 ms

    heatmap.com costs a phone 251 ms of main-thread work and 111 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.

  • Google Tag Manager adds 179 ms

    179 ms

    Google Tag Manager costs a phone 179 ms of main-thread work and 514 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,286 HTML elements

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

  • Klaviyo adds 142 ms

    142 ms

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

  • Shopify adds 94 ms

    94 ms

    Shopify costs a phone 94 ms of main-thread work and 327 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 · 50 KiB

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

  • Reduce unused CSS

    150 ms · 85 KiB

    About 85 KiB of CSS is downloaded but never applied on this page. 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 131 ms. During a long task the page ignores taps.

  • Minify CSS

    7 KiB

    7 KiB could be saved by minifying CSS.

  • Minify JavaScript

    7 KiB

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

1 checks passed
  • Server response: 15 ms

    15 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 13.8 s

    13.8 s

    Your largest element takes 13.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A husky puppy eating from a bowl, surrounded by A Pup Above…”.

  • Speed Index: 15.2 s

    15.2 s

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

  • Time to Interactive: 21.1 s

    21.1 s

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

  • First Contentful Paint: 2.8 s

    2.8 s

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

  • 1 image without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

9 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.3 s

    1.3 s

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

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

    1.1 s

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

  • Real-user TTFB: 409 ms

    409 ms

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

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

    -35%

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

  • Total Blocking Time: 88 ms

    88 ms

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

4 to fix35
  • Page weight: 5.1 MB in 487 requests

    5.1 MB

    Your homepage downloads 5.1 MB in 487 requests on a phone: scripts 2.1 MB (119), other files 1.5 MB (313) and images 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    dd-value-prop-sous-vide-bowl.webp weighs 2.3 MB. On a phone connection a single image that size takes seconds.

  • 2 images in older formats

    2 images (2.6 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.

  • 1 image far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example Turducken-3lb-IngredientsSection.png at 389 px wide, shown at 12 px. Resized copies would save about 68 KiB.

  • About 1.5 g of CO₂ per visit

    1.45 g

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

1 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

5 to fixGoogle 9493
  • 4 text elements with low contrast

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

  • Orphan list items

    Some list items are not inside a list.

  • 12 images without alt text

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

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

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

  • 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
  • 54 automated accessibility rules passed

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

SEO

2 to fixGoogle 10085
  • No H1 headline

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

  • Meta description is long (216 characters)

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

  • 136 internal links, 12 external

    The homepage links to 136 pages on apupabove.com and 12 external pages.

6 checks passed
  • Title: 59 characters

    Your title is a healthy 59 characters: “A Pup Above – Sous-Vide & Bone Broth Infused Fresh Dog Food”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization 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://apupabove.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 (1,934 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

4 to fix68
  • 1 page without a title

    https://apupabove.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

    https://apupabove.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://apupabove.com/blogs/all, https://apupabove.com/customer_authentication/redirect and https://apupabove.com/pages/dd-new-quiz have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 pages without an H1

    https://apupabove.com/customer_authentication/redirect and https://apupabove.com/pages/dd-new-quiz 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 33 found) and read each the way a search engine does.

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

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 5 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix86
  • 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.

  • About 911 words of copy

    The homepage carries about 911 words of visible text.

6 checks passed
  • 29 calls to action

    The homepage has 29 calls to action, for example “SHOP NOW”, “Shop” and “Shop All”.

  • 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: 39 testimonial or review blocks, a star rating and 17 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

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

  • 36 cookies set on arrival

    36

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

  • 49 other companies contacted

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

Apps on your store

Your storefront loads 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Intelligems A B Testing · Wyllo Formerly Nofraud · Elevar Conversion Tracking · Klaviyo Email Marketing Sms · Triplewhale · Okendo · Keepcart Coupon Protect · Aftersell · cloudfront.net · richpanel.com

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

Company

Headquarters
Lewisville

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on apupabove.com, including 18 speed issues, 2 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