Website review, no card needed
alooui.com website review
Visit site (opens in a new tab)Reviewed 20 November 202637 issues · 92 checks
This review found 37 issues worth fixing on alooui.com, 14 of them high impact, across 92 checks. The most urgent: main-thread work: 9.4 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
80B- #47,567 of 121,612 reviewed websitesbeats 55%
- #31,583 of 68,795 online storesbeats 48%
- #30,371 of 62,685 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.5 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.4 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.0 s |
| Sep 5, 2026 | 2.0 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.2 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.1 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 258 ms |
| Jun 27, 2026 | 281 ms |
| Jul 4, 2026 | 297 ms |
| Jul 11, 2026 | 284 ms |
| Jul 18, 2026 | 222 ms |
| Jul 25, 2026 | 188 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 173 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 189 ms |
| Sep 5, 2026 | 208 ms |
| Sep 12, 2026 | 233 ms |
| Sep 19, 2026 | 248 ms |
| Sep 26, 2026 | 286 ms |
| Oct 3, 2026 | 261 ms |
| Oct 10, 2026 | 243 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 238 ms |
| Oct 31, 2026 | 212 ms |
| Nov 7, 2026 | 206 ms |
| Nov 14, 2026 | 245 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
Main-thread work: 9.4 s
A phone's processor spends 9.4 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,941 HTML elements
The page has 4,941 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google CDN and Clarity and others), adding 1.7 MB and 1.4 s of main-thread time.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
650 ms9 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Shopify adds 497 ms
497 msShopify costs a phone 497 ms of main-thread work and 986 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.
Reduce unused JavaScript
564 KiBAbout 564 KiB of JavaScript is downloaded but never used on this page.
Google CDN adds 336 ms
336 msGoogle CDN costs a phone 336 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 301 ms. During a long task the page ignores taps.
Clarity adds 276 ms
276 msClarity costs a phone 276 ms of main-thread work and 32 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.
azurefd.net adds 143 ms
143 msazurefd.net costs a phone 143 ms of main-thread work and 315 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
150 ms · 28 KiB1 image could be 28 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
97 KiB9 files are served with short cache lifetimes, so returning visitors download them again (97 KiB).
Reduce unused CSS
37 KiBAbout 37 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 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.
Legacy JavaScript
4 KiBPolyfills for old browsers add 4 KiB JavaScript that modern phones do not need.
1 checks passed
Server response: 16 ms
16 msYour server sent the HTML in 16 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.
Time to Interactive: 17.5 s
17.5 sThe page becomes fully interactive after 17.5 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 4.1 s
4.1 sYour largest element takes 4.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Real-user INP: 242 ms
242 msReal visitors wait 242 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user TTFB: 809 ms
809 msReal visitors wait 809 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
7 checks passed
Real-user LCP: 1.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 258 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 38% faster for real visitors
-38%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.053
0.053The layout barely moves while loading (CLS 0.053, 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: 3.3 MB in 421 requests
3.3 MBYour homepage downloads 3.3 MB in 421 requests on a phone: scripts 1.5 MB (171), other files 1.2 MB (171) and images 200 KiB (23). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (72 KiB) is 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 0.9 g of CO₂ per visit
0.93 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.93 g of CO₂e: 111.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Invalid ARIA attributes
1 element use ARIA attributes their role does not allow, which confuses screen readers.
20 text elements with low contrast
20 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
17 tap targets too small
17 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
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 (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (37 elements)
Alternative text of images should not be repeated as text: 37 elements on the page fail this check, rated minor by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Table header text should not be empty (1 element)
Table header text should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
<td> elements in a large <table> do not have table headers.
<td> elements in a large <table> do not have table headers. (1 element).
2 checks passed
Every image has alt text
All 136 images in the HTML carry an alt attribute.
59 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 70 WCAG 2.2 A/AA and best-practice rules on the phone render: 59 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
255 internal links, 13 external
The homepage links to 255 pages on alooui.com and 13 external pages.
8 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “Compare AloOui travel eSIM plans for 200+ destinations. Choose fixed or unlimited data, review coverage and validity, a…”.
One H1 headline
Your main headline reads: “Best Travel eSIM | 200+ Countries From $2.99 | AloOui”.
Title: 53 characters
Your title is a healthy 53 characters: “Best Travel eSIM | 200+ Countries From $2.99 | AloOui”.
Canonical URL set
The canonical URL is https://www.alooui.com/.
Structured data in place
Structured data found: FAQPage, Organization, WebPage 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://www.alooui.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,671 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alooui.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without an H1
https://www.alooui.com/collections/best-asia-esim, https://www.alooui.com/collections/unlimited-premium-esim and https://www.alooui.com/collections/unlimited have 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 156 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages 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 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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 2,527 words of copy
The homepage carries about 2,527 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Contact information”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, 1 customer or partner logo, a star rating and 2 trust badges.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 5 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.
31 cookies set on arrival
31Opening the homepage sets 31 cookies, 4 of them by other companies (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.
45 other companies contacted
Loading the homepage contacts 45 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 alooui.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- AVADA Commerce;Shopify;Shopify Plus
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on alooui.com, including 18 speed 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.