Website review, no card needed
agoro.com website review
Visit site (opens in a new tab)Reviewed 19 November 202640 issues · 86 checks
This review found 40 issues worth fixing on agoro.com, 18 of them high impact, across 86 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- #92,121 of 118,550 reviewed websitesbeats 19%
- #57,258 of 67,341 online storesbeats 12%
- #53,434 of 61,402 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 535 ms |
| Jun 6, 2026 | 537 ms |
| Jun 13, 2026 | 470 ms |
| Jun 20, 2026 | 479 ms |
| Jun 27, 2026 | 462 ms |
| Jul 4, 2026 | 470 ms |
| Jul 11, 2026 | 502 ms |
| Jul 18, 2026 | 475 ms |
| Jul 25, 2026 | 459 ms |
| Aug 1, 2026 | 454 ms |
| Aug 8, 2026 | 532 ms |
| Aug 15, 2026 | 531 ms |
| Aug 22, 2026 | 560 ms |
| Aug 29, 2026 | 596 ms |
| Sep 5, 2026 | 540 ms |
| Sep 12, 2026 | 582 ms |
| Sep 19, 2026 | 579 ms |
| Sep 26, 2026 | 598 ms |
| Oct 3, 2026 | 603 ms |
| Oct 10, 2026 | 596 ms |
| Oct 17, 2026 | 609 ms |
| Oct 24, 2026 | 603 ms |
| Oct 31, 2026 | 620 ms |
| Nov 7, 2026 | 643 ms |
| Nov 14, 2026 | 686 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.2 s28 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
11,964 HTML elements
The page has 11,964 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 28
28/100Your mobile performance score is 28. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 4.2 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 (Google Tag Manager, minmaxify.com and TikTok and others), adding 1.4 MB and 1.6 s of main-thread time.
Reduce unused JavaScript
300 ms · 609 KiBAbout 609 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
450 ms · 213 KiB15 files are served with short cache lifetimes, so returning visitors download them again (213 KiB).
Google Tag Manager adds 587 ms
587 msGoogle Tag Manager costs a phone 587 ms of main-thread work and 529 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.
Improve image delivery
400 ms · 76 KiB4 images could be 76 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Shopify adds 151 ms
151 msShopify costs a phone 151 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Legacy JavaScript
40 KiBPolyfills for old browsers add 40 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.
Duplicated JavaScript
2 KiB2 KiB JavaScript is shipped twice across bundles.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 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: 594 ms
594 msReal visitors wait 594 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Largest Contentful Paint: 7.9 s
7.9 sYour largest element takes 7.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Hero banner”.
Time to Interactive: 18.1 s
18.1 sThe page becomes fully interactive after 18.1 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.635
0.635The layout shifts by 0.635 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 681 ms
681 msScripts block taps and scrolling for 681 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 535 ms to 686 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.1 s
2.1 sThe first text or image appears after 2.1 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.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-14, 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.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 514 ms
514 msReal visitors wait 514 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 4.2 MB in 376 requests
4.2 MBYour homepage downloads 4.2 MB in 376 requests on a phone: scripts 1.7 MB (114), images 1.2 MB (73) and other files 885 KiB (130). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
183 KiB3 images are downloaded at several times the size a phone draws them, for example Dark_Knight_Blind_Box_Blog_Post_1740x960_8c965c11-a5e0-4f0a- at 1,740 px wide, shown at 168 px. Resized copies would save about 183 KiB.
1 image below the first screen load straight away
1 image further down the page (75 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.20 g of CO₂e: 143.9 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
Certain ARIA roles must be contained by particular parents (2 elements)
Certain ARIA roles must be contained by particular parents: 2 elements on the page fail this check, rated critical by axe-core.
ARIA attributes must conform to valid values (2 elements)
ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.
ARIA roles used must conform to valid values (1 element)
ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.
ARIA commands must have an accessible name (1 element)
ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (212 characters)
Your meta description is 212 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("//www.agoro.com/cdn/shop/files/Agoro_Black_512px_medium…”.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
247 internal links, 1 external
The homepage links to 247 pages on agoro.com and 1 external page.
5 checks passed
Title: 34 characters
Your title is a healthy 34 characters: “Agoro | Collectibles Made Precious”.
Canonical URL set
The canonical URL is https://www.agoro.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://nzmint.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.agoro.com/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.
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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (3,243 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.agoro.com/products/cars-lightning-mcqueen-mater-blind-box 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 109 found) and read each the way a search engine does.
6 checks passed
Linked pages load
1 page of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
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 1 page that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'app')”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Requests the notification permission on page load
Requests the notification permission on page load.
2 checks passed
Tap targets are thumb-sized
71 of 79 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 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 1,595 words of copy
The homepage carries about 1,595 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
28 calls to action
The homepage has 28 calls to action, for example “Shop all”, “Buy Now” and “Shop Now”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 12 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
32 other companies contacted
Loading the homepage contacts 32 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 agoro.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 12 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Microsoft Clarity · Klaviyo Email Marketing Sms · Triplewhale · Elevar Conversion Tracking · Minmaxify Order Limits · Pagefly Ai Page Builder · Gdpr Cookie Consent · Fish Wishlist · Pushowl · nfusionsolutions.com · Swym Wishlist Plus
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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on agoro.com, including 20 speed issues, 4 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.