Website review, no card needed

thepuzzlefeeder.com logo

thepuzzlefeeder.com website review

Visit site (opens in a new tab)Reviewed 16 November 202624 issues · 85 checks

This review found 24 issues worth fixing on thepuzzlefeeder.com, 11 of them high impact, across 85 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.7 s1.3 sJun 6Nov 141.6 s
Show as table
DateReal-visitor load time (LCP)
Jun 6, 20262.6 s
Jun 13, 20263.0 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20263.0 s
Jul 11, 20262.7 s
Jul 18, 20262.9 s
Jul 25, 20262.8 s
Aug 1, 20262.7 s
Aug 8, 20262.8 s
Aug 15, 20262.9 s
Aug 22, 20263.3 s
Aug 29, 20263.4 s
Sep 5, 20262.9 s
Sep 12, 20262.5 s
Sep 19, 20262.1 s
Sep 26, 20261.8 s
Oct 3, 20261.8 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.9 s
Oct 31, 20262.0 s
Nov 7, 20261.6 s
Nov 14, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
127 ms84 msMay 30Nov 14110 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026103 ms
Jun 6, 2026102 ms
Jun 13, 2026102 ms
Jun 20, 202696 ms
Jun 27, 202689 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 2026104 ms
Jul 25, 2026110 ms
Aug 1, 2026104 ms
Aug 8, 2026116 ms
Aug 15, 2026122 ms
Aug 22, 2026113 ms
Aug 29, 2026122 ms
Sep 5, 2026111 ms
Oct 24, 2026105 ms
Oct 31, 2026106 ms
Nov 7, 2026104 ms
Nov 14, 2026110 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 thepuzzlefeeder.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. thepuzzlefeeder.com at 1.1 s1.1 s
  2. thepuzzlefeeder.com at 2.2 s2.2 s
  3. thepuzzlefeeder.com at 3.3 s3.3 s
  4. thepuzzlefeeder.com at 4.4 s4.4 s
  5. thepuzzlefeeder.com at 5.5 s5.5 s
  6. thepuzzlefeeder.com at 6.6 s6.6 s
  7. thepuzzlefeeder.com at 7.7 s7.7 s
  8. thepuzzlefeeder.com at 8.8 s8.8 s

Speed

9 to fix54
  • Reduce unused JavaScript

    10.4 s · 1.6 MB

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

  • Minify JavaScript

    4.8 s · 365 KiB

    365 KiB could be saved by minifying JavaScript.

  • Main-thread work: 6.4 s

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

  • Improve image delivery

    450 ms · 2.3 MB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (mediadelivery.net, Shopify and Klaviyo and others), adding 3.7 MB and 1.4 s of main-thread time.

  • Mobile performance score: 54

    54/100

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

  • mediadelivery.net adds 633 ms

    633 ms

    mediadelivery.net costs a phone 633 ms of main-thread work and 1.9 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.

  • Shopify adds 624 ms

    624 ms

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

  • 2,653 HTML elements

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

  • Reduce unused CSS

    290 ms · 60 KiB

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

  • 7 long tasks on the main thread

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

  • Render-blocking requests

    150 ms

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

  • Use efficient cache lifetimes

    50 ms · 34 KiB

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

  • Font display

    50 ms

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

  • Legacy JavaScript

    19 KiB

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

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 12 ms

    12 ms

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

Core Web Vitals

4 to fix100
  • First Contentful Paint: 13.7 s

    13.7 s

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

  • Largest Contentful Paint: 29.6 s

    29.6 s

    Your largest element takes 29.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A corgi eagerly munches from a clever puzzle feeder, akin t…”.

  • Time to Interactive: 32.0 s

    32.0 s

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

  • Speed Index: 13.7 s

    13.7 s

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

  • Tap response (INP) held steady for real visitors

    +4%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 103 ms to 110 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.6 s

    1.6 s

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

  • Real-user INP: 110 ms

    110 ms

    Real visitors wait 110 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: 491 ms

    491 ms

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

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

    -43%

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

  • Total Blocking Time: 147 ms

    147 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix70
  • Page weight: 8.1 MB in 597 requests

    8.1 MB

    Your homepage downloads 8.1 MB in 597 requests on a phone: scripts 3.2 MB (297), images 2.9 MB (23) and other files 1.2 MB (210). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.29 g

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

4 to fixGoogle 9494
  • Hidden but focusable

    9 elements hidden from screen readers can still receive keyboard focus.

  • 9 text elements with low contrast

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

  • Frames without titles

    3 frames have no title, so screen-reader users cannot tell what they contain.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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. (2 elements).

2 checks passed
  • Every image has alt text

    All 45 images in the HTML carry an alt attribute.

  • 53 automated accessibility rules passed

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

SEO

1 to fixGoogle 10095
  • Meta description is long (187 characters)

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

  • 109 internal links, 19 external

    The homepage links to 109 pages on thepuzzlefeeder.com and 19 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “PuzzleFeeder™ - Slower than a slow feeder”.

  • Title: 54 characters

    Your title is a healthy 54 characters: “Puzzle Feeder | Slow Feeder Dog Bowls & Puzzle Feeders”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, FAQPage, Organization, PetStore 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://thepuzzlefeeder.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://thepuzzlefeeder.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.

3 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,434 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 34 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    7 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

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

  • Every page has a meta description

    All 7 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 7 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 7 small tap targets

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

  • 3 JavaScript errors while loading

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

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix90
  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No analytics detected

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 595 words of copy

    The homepage carries about 595 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Now”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “SHOP ALL”, “Contact Us” and “Shop Now”.

  • 11 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block and a star rating.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

  • 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
  • 5 trackers load before any consent

    5

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

  • 14 cookies set on arrival

    14

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 thepuzzlefeeder.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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Sami B2b Lock · Klaviyo Email Marketing Sms · Uppromote Affiliate · Sami Wholesale · Seowill Ai Seo · Inbox · Tinyseo Ai Seo Speed · Judge Me Reviews · Bss B2b Solution · Pagefly Ai Page Builder · Wholesale Lock Hide Price · Stape Remix · Affliate By Secomapp · bsscommerce.com · cloudfront.net · gropulse.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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on thepuzzlefeeder.com, including 13 speed issues, 1 SEO issue 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