Website review, no card needed
dokidokicos.com website review
Visit site (opens in a new tab)Reviewed 4 November 202633 issues · 80 checks
This review found 33 issues worth fixing on dokidokicos.com, 13 of them high impact, across 80 checks. The most urgent: main-thread work: 15.0 s. 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
78C- #62,123 of 123,940 reviewed websitesbeats 44%
- #40,543 of 69,719 online storesbeats 36%
- #38,716 of 63,424 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.1 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.0 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 289 ms |
| May 23, 2026 | 312 ms |
| May 30, 2026 | 304 ms |
| Jun 6, 2026 | 307 ms |
| Jun 13, 2026 | 291 ms |
| Jun 20, 2026 | 273 ms |
| Jun 27, 2026 | 260 ms |
| Jul 4, 2026 | 238 ms |
| Jul 11, 2026 | 231 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 237 ms |
| Aug 8, 2026 | 237 ms |
| Aug 15, 2026 | 231 ms |
| Aug 22, 2026 | 223 ms |
| Aug 29, 2026 | 223 ms |
| Sep 5, 2026 | 224 ms |
| Sep 12, 2026 | 228 ms |
| Sep 19, 2026 | 235 ms |
| Sep 26, 2026 | 241 ms |
| Oct 3, 2026 | 246 ms |
| Oct 10, 2026 | 251 ms |
| Oct 17, 2026 | 257 ms |
| Oct 24, 2026 | 250 ms |
| Oct 31, 2026 | 237 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
1.0 s
2.0 s
3.1 s
4.1 s
5.1 s
6.1 s
7.1 s
8.1 s
Speed
Main-thread work: 15.0 s
A phone's processor spends 15.0 s on main-thread work while loading, 5.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.3 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
6,953 HTML elements
The page has 6,953 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
900 ms · 6.5 MB115 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, pop-convert.com and xcottons.com and others), adding 2.1 MB and 1.4 s of main-thread time.
Shopify adds 901 ms
901 msShopify costs a phone 901 ms of main-thread work and 1.1 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.
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
859 KiBAbout 859 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
317 KiB8 files are served with short cache lifetimes, so returning visitors download them again (317 KiB).
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 267 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Reduce unused CSS
27 KiBAbout 27 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
6 KiB6 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: 11 ms
11 msYour server sent the HTML in 11 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.
Real-user INP: 714 ms
714 msReal visitors wait 714 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Time to Interactive: 28.2 s
28.2 sThe page becomes fully interactive after 28.2 s. Good is under 3.8 s.
Largest Contentful Paint: 6.7 s
6.7 sYour largest element takes 6.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 671 ms
671 msScripts block taps and scrolling for 671 ms in total while the page loads. Good is under 200 ms.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
8 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 778 ms
778 msReal visitors wait 778 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 289 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.071
0.071The layout barely moves while loading (CLS 0.071, good is under 0.1).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 14.2 MB in 721 requests
14.2 MBYour homepage downloads 14.2 MB in 721 requests on a phone: images 10.5 MB (391), scripts 2.0 MB (110) and other files 1.2 MB (181). Under 2 MB keeps phones on slow connections fast.
25 images below the first screen load straight away
25 images further down the page (734 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
70 KiB1 image is downloaded at several times the size a phone draws it, for example 3126d1d019035e450c4ae65b7022b074.png at 942 px wide, shown at 84 px. Resized copies would save about 70 KiB.
About 4.0 g of CO₂ per visit
4.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.01 g of CO₂e: 481.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Summary elements must have discernible text (1 element)
Summary elements must have discernible text: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 4 mores 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 robots.txt
There is no robots.txt at dokidokicos.com/robots.txt, the first file search crawlers ask for.
456 internal links, 11 external
The homepage links to 456 pages on dokidokicos.com and 11 external pages.
6 checks passed
Meta description: 133 characters
Your meta description is 133 characters: “Worldwide Delivery Online Cosplay Shop--High Quality & Unique Ranking System Of Anime Cosplay ,Game Cosplay ,Movie Cosp…”.
Title: 59 characters
Your title is a healthy 59 characters: “Halloween Ready: 2,000+ Cosplays in Stock – dokidokicosplay”.
Canonical URL set
The canonical URL is https://dokidokicos.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.
XML sitemap found
Your XML sitemap is reachable at https://dokidokicos.com/sitemap.xml.
AI search readiness
3 checks passed
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 (3,258 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dokidokicos.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without a meta description
https://dokidokicos.com/collections/genshin-impact, https://dokidokicos.com/collections/gachiakuta, https://dokidokicos.com/collections/honkai-star-rail, https://dokidokicos.com/collections/love-and-deepspace, https://dokidokicos.com/collections/witch-hat-atelier and https://dokidokicos.com/collections/zenless-zone-zero and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://dokidokicos.com/collections/genshin-impact, https://dokidokicos.com/collections/gachiakuta, https://dokidokicos.com/collections/honkai-star-rail, https://dokidokicos.com/collections/love-and-deepspace, https://dokidokicos.com/collections/witch-hat-atelier and https://dokidokicos.com/collections/zenless-zone-zero and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages with very little text
https://dokidokicos.com/collections/gachiakuta, https://dokidokicos.com/collections/arrcane, https://dokidokicos.com/collections/alienn-stage and https://dokidokicos.com/collections/puella-magi-madoka-magica 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.
1 page slow to respond
https://dokidokicos.com/collections/gachiakuta took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 189 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
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
94 of 98 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 2,024 words of copy
The homepage carries about 2,024 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: “Shop Weekly Recommendation” and “Start Shopping”.
9 calls to action
The homepage has 9 calls to action, for example “Shop Weekly Recommendation”, “Shop NEW Costumes” and “Shop Arriving Soon · First Batch”.
4 short forms
4 short forms (1 field at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 191 testimonial or review blocks and 1 trust badge.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager 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.
25 cookies set on arrival
25Opening the homepage sets 25 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.
43 other companies contacted
Loading the homepage contacts 43 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 dokidokicos.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- 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 33 issues on dokidokicos.com, including 16 speed issues, 2 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.