Website review, no card needed
minipetmart.net website review
Visit site (opens in a new tab)Reviewed 14 November 202618 issues · 77 checks
This review found 18 issues worth fixing on minipetmart.net, 4 of them high impact, across 77 checks. The most urgent: render-blocking requests. 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
Site score
89BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 875 ms |
| May 30, 2026 | 912 ms |
| Jun 6, 2026 | 871 ms |
| Jun 13, 2026 | 856 ms |
| Jun 20, 2026 | 891 ms |
| Jun 27, 2026 | 900 ms |
| Jul 4, 2026 | 920 ms |
| Jul 11, 2026 | 921 ms |
| Jul 18, 2026 | 923 ms |
| Jul 25, 2026 | 941 ms |
| Aug 1, 2026 | 937 ms |
| Aug 8, 2026 | 927 ms |
| Aug 15, 2026 | 915 ms |
| Aug 22, 2026 | 842 ms |
| Aug 29, 2026 | 843 ms |
| Sep 5, 2026 | 839 ms |
| Sep 12, 2026 | 818 ms |
| Sep 19, 2026 | 841 ms |
| Sep 26, 2026 | 827 ms |
| Oct 3, 2026 | 835 ms |
| Oct 10, 2026 | 837 ms |
| Oct 17, 2026 | 846 ms |
| Oct 24, 2026 | 870 ms |
| Oct 31, 2026 | 851 ms |
| Nov 7, 2026 | 825 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 72 ms |
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 79 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 77 ms |
| Jul 18, 2026 | 78 ms |
| Jul 25, 2026 | 77 ms |
| Aug 1, 2026 | 78 ms |
| Aug 8, 2026 | 79 ms |
| Aug 15, 2026 | 78 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 75 ms |
| Sep 5, 2026 | 73 ms |
| Sep 12, 2026 | 73 ms |
| Sep 19, 2026 | 72 ms |
| Sep 26, 2026 | 72 ms |
| Oct 3, 2026 | 74 ms |
| Oct 10, 2026 | 77 ms |
| Oct 17, 2026 | 77 ms |
| Oct 24, 2026 | 77 ms |
| Oct 31, 2026 | 75 ms |
| Nov 7, 2026 | 72 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
1.0 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Google Tag Manager adds 181 ms
181 msGoogle Tag Manager costs a phone 181 ms of main-thread work and 317 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.
Reduce unused JavaScript
150 ms · 209 KiBAbout 209 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Google Fonts), adding 366 KiB and 202 ms of main-thread time.
Reduce unused CSS
150 ms · 31 KiBAbout 31 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 77 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
16 KiB1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).
Improve image delivery
9 KiB1 image could be 9 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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.
3 checks passed
Mobile performance score: 96
96/100Your mobile performance score is 96. That is in Google's “good” band (90 and up).
Main-thread work: 0.5 s
A phone's processor spends 0.5 s on main-thread work while loading, 195 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 5.0 s
5.0 sThe page becomes fully interactive after 5.0 s. Good is under 3.8 s.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Large Selection of Pet Food, Supplies, and Accessories Welc…”.
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-07, real Chrome visitors' tap response (inp) went from 72 ms to 72 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 0.9 s to 0.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
10 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 79 ms
79 msReal visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 761 ms
761 msReal visitors wait 761 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Speed Index: 1.3 s
1.3 sVisually, the page fills in at 1.3 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 53 ms
53 msScripts block the page for only 53 ms while loading. Good is under 200 ms.
Images and page weight
About 0.2 g of CO₂ per visit
0.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.19 g of CO₂e: 22.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 678 KiB in 37 requests
678 KiBYour homepage downloads 678 KiB in 37 requests on a phone: scripts 437 KiB (16), images 132 KiB (10) and stylesheets 44 KiB (4). That is a lean page.
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
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
23 internal links, 1 external
The homepage links to 23 pages on minipetmart.net and 1 external page.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Get top-quality pet supplies and accessories from the company and the brands you trust. Mini Pet Mart has several locat…”.
Title: 50 characters
Your title is a healthy 50 characters: “Mini Pet Mart - Pet Food, Supplies and Accessories”.
Canonical URL set
The canonical URL is https://minipetmart.net/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Place and WebPage.
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://minipetmart.net/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://minipetmart.net/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.
2 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 (511 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages without a meta description
https://minipetmart.net/services, https://minipetmart.net/products, https://minipetmart.net/contact, https://minipetmart.net/customer-reviews, https://minipetmart.net/community-involvement and https://minipetmart.net/gallery and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 10 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.
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 10 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
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.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 308 words of copy
The homepage carries about 308 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn More” and “Get in Touch”.
5 calls to action
The homepage has 5 calls to action, for example “Learn More”, “Contact” and “Get in Touch”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
3 other companies contacted
Loading the homepage contacts 3 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 minipetmart.net, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 18 issues on minipetmart.net, including 5 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.