Website review, no card needed
mikeamiri.com website review
Visit site (opens in a new tab)Reviewed 16 November 202628 issues · 78 checks
This review found 28 issues worth fixing on mikeamiri.com, 4 of them high impact, across 78 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
89B- #3,636 of 116,487 reviewed websitesbeats 95%
- #1,903 of 66,776 online storesbeats 95%
- #1,847 of 60,929 Shopify storesbeats 95%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.2 s |
| Jun 20, 2026 | 3.2 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.4 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.9 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.8 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.5 s |
| Oct 31, 2026 | 3.4 s |
| Nov 7, 2026 | 3.4 s |
| Nov 14, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 164 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 167 ms |
| Jul 4, 2026 | 171 ms |
| Jul 11, 2026 | 169 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 167 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 187 ms |
| Aug 22, 2026 | 207 ms |
| Aug 29, 2026 | 221 ms |
| Sep 5, 2026 | 214 ms |
| Sep 12, 2026 | 193 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 170 ms |
| Oct 3, 2026 | 177 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 202 ms |
| Oct 24, 2026 | 215 ms |
| Oct 31, 2026 | 211 ms |
| Nov 7, 2026 | 195 ms |
| Nov 14, 2026 | 187 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.4 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 76
76/100Your mobile performance score is 76. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
600 ms · 131 KiB6 files are served with short cache lifetimes, so returning visitors download them again (131 KiB).
Improve image delivery
486 KiB16 images could be 486 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2,029 HTML elements
The page has 2,029 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
121 KiBAbout 121 KiB of JavaScript is downloaded but never used on this page.
6 third-party services on the page
6 third-party services load with your homepage (truevaultcdn.com, Cloudflare CDN and Shopify and others), adding 154 KiB and 94 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 71 ms. During a long task the page ignores taps.
Reduce unused CSS
33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
16 KiB16 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.
2 checks passed
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 331 ms of it running JavaScript. That is comfortably low.
Server response: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Cumulative Layout Shift: 0.313
0.313The layout shifts by 0.313 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Time to Interactive: 3.8 s
3.8 sThe page becomes fully interactive after 3.8 s. Good is under 3.8 s.
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) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 161 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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 3.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 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 INP: 183 ms
183 msReal visitors wait 183 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: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 411 ms
411 msReal visitors wait 411 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 2.3 s
2.3 sYour largest element renders in 2.3 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Our Site uses cookies and related technologies to enable ou…”.
Total Blocking Time: 21 ms
21 msScripts block the page for only 21 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 112 requests
2.6 MBYour homepage downloads 2.6 MB in 112 requests on a phone: images 2.1 MB (73), scripts 218 KiB (18) and other files 147 KiB (8). Under 2 MB keeps phones on slow connections fast.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 94 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 3 problems
Structured data found (Organization and WebSite) but with 3 problems, for example “Organization: sameAs is not an absolute URL ("/")”.
One H1 headline
Your <h1> is empty.
338 internal links, 9 external
The homepage links to 338 pages on mikeamiri.com and 9 external pages.
6 checks passed
Meta description: 132 characters
Your meta description is 132 characters: “Shop the AMIRI official site. Discover the latest men's and women's ready to wear, shoes, leather goods and accessories…”.
Title: 49 characters
Your title is a healthy 49 characters: “AMIRI Official Site | Discover The New Collection”.
Canonical URL set
The canonical URL is https://amiri.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://amiri.com/sitemap.xml.
AI search readiness
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://amiri.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages point its canonical at the homepage
https://amiri.com/collections/men and https://amiri.com/collections/women declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
3 pages share a title
/, https://amiri.com/collections/men and https://amiri.com/collections/women all use the title “AMIRI Official Site | Discover The New Collection”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://amiri.com/collections/gifting, https://amiri.com/collections/view-all-sale, https://amiri.com/collections/mens-pre-spring-2027, https://amiri.com/collections/matchday-capsule, https://amiri.com/collections/mens-winter-capsule and https://amiri.com/collections/mens-online-exclusives have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://amiri.com/collections/men and https://amiri.com/collections/women use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://amiri.com/collections/gifting, https://amiri.com/collections/mens-featured and https://amiri.com/collections/mens-pre-spring-2027 have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://amiri.com/collections/women took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 169 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 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 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 139 words
The homepage has only about 139 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP MEN'S NEW ARRIVALS” and “SHOP WOMEN'S NEW ARRIVALS”.
4 calls to action
The homepage has 4 calls to action, for example “SHOP MEN'S NEW ARRIVALS”, “SHOP WOMEN'S NEW ARRIVALS” and “Contact”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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.
30 cookies set on arrival
30Opening the homepage sets 30 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.
25 other companies contacted
Loading the homepage contacts 25 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 mikeamiri.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Klaviyo Email Marketing Sms · Lucky Orange · Microsoft Clarity · Wyllo Formerly Nofraud · Sortd Merchandiser · Kx Ai Collections · Kimonix · global-e.com · botnot.io
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 | Hotjar | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 25 open roles
- Teams
- Miami Design District (3), Brand & Communications (2), E-Commerce (2), Merchandising – DTC (2)
- Job board
- lever
- Careers page
- jobs.lever.co/AMIRI (opens in a new tab)
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on mikeamiri.com, including 10 speed issues, 2 SEO issues and 3 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.