Website review, no card needed
humankindpet.com website review
Visit site (opens in a new tab)Reviewed 9 November 202630 issues · 70 checks
This review found 30 issues worth fixing on humankindpet.com, 11 of them high impact, across 70 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
One score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
5.0 s
Speed
Use efficient cache lifetimes
1.4 s · 235 KiB9 files are served with short cache lifetimes, so returning visitors download them again (235 KiB).
Reduce unused JavaScript
1.4 s · 190 KiBAbout 190 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Improve image delivery
50 ms · 1.9 MB4 images could be 1.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
500 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused CSS
300 ms · 67 KiBAbout 67 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.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Cloudflare CDN and Heap and others), adding 595 KiB and 292 ms of main-thread time.
Legacy JavaScript
150 ms · 32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 92 ms. During a long task the page ignores taps.
Font display
50 msWeb 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 368 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 13.1 s
13.1 sYour largest element takes 13.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.7 s
13.7 sThe page becomes fully interactive after 13.7 s. Good is under 3.8 s.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
Total Blocking Time: 75 ms
75 msScripts block the page for only 75 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
1 image over 500 KB
landing-video.gif weighs 9.4 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (9.4 MB) is 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.
Page weight: 3.8 MB in 179 requests
3.8 MBYour homepage downloads 3.8 MB in 179 requests on a phone: images 2.2 MB (30), other files 777 KiB (95) and scripts 658 KiB (43). Under 2 MB keeps phones on slow connections fast.
About 1.1 g of CO₂ per visit
1.07 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.07 g of CO₂e: 128.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
<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.
24 images without alt text
24 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
Table header text should not be empty (1 element)
Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h1 → h3), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
21 H1 headlines
There are 21 <h1> headlines (“Humankind®:”, “100%” and “99.9%”). One clear main headline is easier for people and search engines.
Meta description is long (220 characters)
Your meta description is 220 characters; Google truncates after about 160, so the end of your pitch is cut.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
31 internal links, 3 external
The homepage links to 31 pages on humankindpet.com and 3 external pages.
5 checks passed
Title: 42 characters
Your title is a healthy 42 characters: “Humankind | 100% Human-Grade Food for Pets”.
Canonical URL set
The canonical URL is https://humankindpet.com/.
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://humankindpet.com/sitemap.xml.
AI search readiness
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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,920 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://humankindpet.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
1 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Best practices
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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
11 of 11 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
About 577 words of copy
The homepage carries about 577 words of visible text.
5 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Shop Now”, “register” and “get started”.
4 short forms
4 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Meta Pixel and Heap.
Direct contact links
Visitors can reach you directly: 0 phone links 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
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Heap 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
18 other companies contacted
Loading the homepage contacts 18 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 humankindpet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- The footer still says © 2024.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Heap
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on humankindpet.com, including 11 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.