Website review, no card needed
pawstar.com website review
Visit site (opens in a new tab)Reviewed 8 November 202641 issues · 88 checks
This review found 41 issues worth fixing on pawstar.com, 15 of them high impact, across 88 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
72C- #86,140 of 110,527 reviewed websitesbeats 19%
- #53,536 of 62,894 online storesbeats 12%
- #49,995 of 57,406 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 122 ms |
| May 23, 2026 | 121 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 122 ms |
| Jun 27, 2026 | 123 ms |
| Jul 4, 2026 | 122 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 125 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 150 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 245 ms |
| Sep 26, 2026 | 264 ms |
| Oct 3, 2026 | 276 ms |
| Oct 10, 2026 | 303 ms |
| Oct 17, 2026 | 295 ms |
| Oct 24, 2026 | 281 ms |
| Oct 31, 2026 | 280 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
Speed
Render-blocking requests
1.6 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
1.1 s · 248 KiB9 images could be 248 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Shopify adds 1.1 s
1.1 sShopify costs a phone 1.1 s of main-thread work and 1.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,077 HTML elements
The page has 8,077 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 7.2 s
A phone's processor spends 7.2 s on main-thread work while loading, 2.3 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 (Shopify, Google CDN and willdesk.com and others), adding 2.1 MB and 1.4 s of main-thread time.
Reduce unused JavaScript
624 KiBAbout 624 KiB of JavaScript is downloaded but never used on this page.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 555 ms. During a long task the page ignores taps.
Google CDN adds 189 ms
189 msGoogle CDN costs a phone 189 ms of main-thread work and 298 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Reduce unused CSS
170 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 170 ms faster on a phone.
Use efficient cache lifetimes
100 ms · 56 KiB9 files are served with short cache lifetimes, so returning visitors download them again (56 KiB).
Minify JavaScript
60 ms · 64 KiB64 KiB could be saved by minifying JavaScript.
Legacy JavaScript
7 KiBPolyfills for old browsers add 7 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
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 63 ms
63 msYour server sent the HTML in 63 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 8.6 s
8.6 sYour largest element takes 8.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Color-Swap Hoodies Just Got Better! Choose from even more e…”.
Time to Interactive: 22.0 s
22.0 sThe page becomes fully interactive after 22.0 s. Good is under 3.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user INP: 362 ms
362 msReal visitors wait 362 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 131% slower for real visitors
+131%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 122 ms to 280 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.05
0.05For real visitors the layout shifts by 0.05 (75th percentile). Good is under 0.1.
Real-user TTFB: 482 ms
482 msReal visitors wait 482 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 6.2 MB in 420 requests
6.2 MBYour homepage downloads 6.2 MB in 420 requests on a phone: images 2.8 MB (44), scripts 1.8 MB (201) and other files 1.1 MB (145). Under 2 MB keeps phones on slow connections fast.
5 images below the first screen load straight away
5 images further down the page (673 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
2 images in older formats
2 images (119 KiB) 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.
About 1.7 g of CO₂ per visit
1.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.74 g of CO₂e: 209.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
10 form fields without a label
10 form fields have no label, so screen readers announce an empty box and autofill guesses.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
SEO
Title is short (24 characters)
Your title is only 24 characters: “Pawstar Official Website”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (248 characters)
Your meta description is 248 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
232 internal links, 16 external
The homepage links to 232 pages on pawstar.com and 16 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Pawstar”.
Canonical URL set
The canonical URL is https://pawstar.com/.
Structured data in place
Structured data found: Organization.
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://pawstar.com/sitemap.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.
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,980 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://pawstar.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://pawstar.com/pages/pawstar-events-2026, https://pawstar.com/blogs/all-blogs, https://pawstar.com/pages/club-pawstar, https://pawstar.com/a/self-faq, https://pawstar.com/pages/about-us and https://pawstar.com/collections/attachment have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://pawstar.com/collections/ear-color-swap, https://pawstar.com/collections/canine, https://pawstar.com/collections/feline-ears, https://pawstar.com/collections/bunny-ears, https://pawstar.com/collections/other-animals and https://pawstar.com/collections/ears use the same meta description. A description written for each page earns more clicks.
15 pages without an H1
https://pawstar.com/pages/paw-store, https://pawstar.com/products/tickets-ghost, https://pawstar.com/pages/pawstar-events-2026, https://pawstar.com/pages/contact, https://pawstar.com/blogs/all-blogs and https://pawstar.com/pages/club-pawstar and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://pawstar.com/pages/paw-store, https://pawstar.com/products/tickets-ghost, https://pawstar.com/pages/pawstar-events-2026, https://pawstar.com/pages/contact, https://pawstar.com/blogs/all-blogs and https://pawstar.com/pages/club-pawstar and 6 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 104 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://pawstar.com/.
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
41 of 43 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 499 words of copy
The homepage carries about 499 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Sign up — it takes a minute”.
2 calls to action
The homepage has 2 calls to action, for example “►Contact US”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
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
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Tag Manager, Meta Pixel, Pinterest Tag and TikTok 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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
26 other companies contacted
Loading the homepage contacts 26 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 pawstar.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 14 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Powerful Form Builder · Seolab · Judge Me Reviews · Google Youtube · Joy Loyalty Program · Bixgrow Affiliate · Globo Product Options · Swym Wishlist Plus · Glo Color Swatch · Willdesk Live Chat Helpdesk · Forms · Simplee Memberships · Calee · printful.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
Company
- Headquarters
- Racine
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on pawstar.com, including 19 speed issues, 4 SEO issues and 5 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.