Website review, no card needed
coosnkisses.com website review
Visit site (opens in a new tab)Reviewed 20 November 202636 issues · 77 checks
This review found 36 issues worth fixing on coosnkisses.com, 14 of them high impact, across 77 checks. The most urgent: reduce unused JavaScript. 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
73C- #91,493 of 123,845 reviewed websitesbeats 23%
- #57,021 of 69,695 online storesbeats 15%
- #53,346 of 63,403 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.2 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Reduce unused JavaScript
2.0 s · 587 KiBAbout 587 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Mobile performance score: 48
48/100Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,211 HTML elements
The page has 3,211 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Shopify, shiprocket.in and smile.io and others), adding 1.6 MB and 1.3 s of main-thread time.
Improve image delivery
350 ms · 493 KiB41 images could be 493 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.
Shopify adds 690 ms
690 msShopify costs a phone 690 ms of main-thread work and 1.4 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.
shiprocket.in adds 561 ms
561 msshiprocket.in costs a phone 561 ms of main-thread work and 76 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
400 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 292 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 54 KiBAbout 54 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.
Use efficient cache lifetimes
150 ms · 46 KiB3 files are served with short cache lifetimes, so returning visitors download them again (46 KiB).
Duplicated JavaScript
14 KiB14 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
9 KiB9 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 12.9 s
12.9 sYour largest element takes 12.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 16.3 s
16.3 sThe page becomes fully interactive after 16.3 s. Good is under 3.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Total Blocking Time: 577 ms
577 msScripts block taps and scrolling for 577 ms in total while the page loads. Good is under 200 ms.
6 images without width and height
6 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.
1 checks passed
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 345 requests
5.1 MBYour homepage downloads 5.1 MB in 345 requests on a phone: images 2.3 MB (71), scripts 1.4 MB (75) and other files 1.1 MB (155). Under 2 MB keeps phones on slow connections fast.
2 images below the first screen load straight away
2 images further down the page (58 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
11 text elements with low contrast
11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (11 elements)
All page content should be contained by landmarks: 11 elements on the page fail this check, rated moderate by axe-core.
16 form fields without a label
16 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (7 elements)
Alternative text of images should not be repeated as text: 7 elements on the page fail this check, rated minor by axe-core.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 96 images in the HTML carry an alt attribute.
51 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: 51 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
189 internal links, 6 external
The homepage links to 189 pages on coosnkisses.com and 6 external pages.
7 checks passed
Meta description: 79 characters
Your meta description is 79 characters: “Baby Crochet Toys | Handmade | Organic | Hemp | Dog Toys | Baby Toys | Pet toys”.
Title: 62 characters
Your title is a healthy 62 characters: “Coos and Kisses | Premium Toys & Accessories | Paws and Kisses”.
Canonical URL set
The canonical URL is https://coosnkisses.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://coosnkisses.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,828 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://coosnkisses.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://coosnkisses.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://coosnkisses.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
1 page without a meta description
https://coosnkisses.com/customer_authentication/redirect has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://coosnkisses.com/customer_authentication/redirect has 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 78 found) and read each the way a search engine does.
2 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.
Best practices
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
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 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
82 of 93 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.
Thin social proof
Social proof on the homepage: 51 testimonial or review blocks. 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 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 955 words of copy
The homepage carries about 955 words of visible text.
2 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Shop by Category” and “Contact Us”.
40 short forms
40 short forms (2 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap 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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
22 other companies contacted
Loading the homepage contacts 22 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 coosnkisses.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Wishlist Hero · Pagefly Ai Page Builder · Judge Me Reviews · Discount Aio Autoketing Code · Forms · Simply Otp Login · shiprocket.in
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
- 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 36 issues on coosnkisses.com, including 16 speed issues, 1 SEO issue and 4 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.