Website review, no card needed
aldoshoes.com.sg website review
Visit site (opens in a new tab)Reviewed 20 November 202647 issues · 92 checks
This review found 47 issues worth fixing on aldoshoes.com.sg, 17 of them high impact, across 92 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
71C- #99,215 of 123,037 reviewed websitesbeats 17%
- #60,836 of 69,400 online storesbeats 10%
- #56,495 of 63,187 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.9 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 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.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.3 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.0 s |
| Nov 14, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 144 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 151 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 151 ms |
| Jul 11, 2026 | 151 ms |
| Jul 18, 2026 | 154 ms |
| Jul 25, 2026 | 157 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 162 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 169 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 171 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 172 ms |
| Oct 31, 2026 | 177 ms |
| Nov 7, 2026 | 172 ms |
| Nov 14, 2026 | 170 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.7 s
3.3 s
5.0 s
6.6 s
8.3 s
9.9 s
11.6 s
13.2 s
Speed
Render-blocking requests
1.4 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Main-thread work: 12.0 s
A phone's processor spends 12.0 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,626 HTML elements
The page has 3,626 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 (Google Tag Manager, Facebook and Shopify and others), adding 2.3 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
150 ms · 856 KiBAbout 856 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 577 ms. During a long task the page ignores taps.
Google Tag Manager adds 538 ms
538 msGoogle Tag Manager costs a phone 538 ms of main-thread work and 353 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.
Shopify adds 432 ms
432 msShopify costs a phone 432 ms of main-thread work and 673 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.
Facebook adds 450 ms
450 msFacebook costs a phone 450 ms of main-thread work and 265 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.
Use efficient cache lifetimes
50 ms · 400 KiB24 files are served with short cache lifetimes, so returning visitors download them again (400 KiB).
Reduce unused CSS
300 ms · 92 KiBAbout 92 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
ZenDesk adds 251 ms
251 msZenDesk costs a phone 251 ms of main-thread work and 360 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.
OptiMonk adds 147 ms
147 msOptiMonk costs a phone 147 ms of main-thread work and 497 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.
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Improve image delivery
31 KiB1 image could be 31 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
14 KiB14 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: 19 ms
19 msYour server sent the HTML in 19 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: 21.5 s
21.5 sThe page becomes fully interactive after 21.5 s. Good is under 3.8 s.
Speed Index: 12.9 s
12.9 sVisually, the page fills in at 12.9 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
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 text “Made for Your Favorite Moments”.
Real-user INP: 217 ms
217 msReal visitors wait 217 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 144 ms to 170 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 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 351 ms
351 msReal visitors wait 351 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.4 MB in 427 requests
5.4 MBYour homepage downloads 5.4 MB in 427 requests on a phone: scripts 2.1 MB (127), images 1.7 MB (77) and other files 1.0 MB (161). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
New_Subscribers_-_Mobile_375x90px.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
2 images far larger than shown
203 KiB2 images are downloaded at several times the size a phone draws them, for example Shop_for_women.png at 1,080 px wide, shown at 82 px. Resized copies would save about 203 KiB.
About 1.5 g of CO₂ per visit
1.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.54 g of CO₂e: 184.4 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
24 text elements with low contrast
24 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Orphan list items
Some list items are not inside a list.
55 images without alt text
55 images have no alt text, which hurts accessibility and image search.
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 form field without a label
1 form field has 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.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 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.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
1 checks passed
49 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: 49 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (19 characters)
Your title is only 19 characters: “Aldoshoes Singapore”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
314 internal links, 5 external
The homepage links to 314 pages on aldoshoes.com.sg and 5 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://www.aldoshoes.com.sg/.
Structured data in place
Structured data found: Organization and WebSite.
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.aldoshoes.com.sg/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,481 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.aldoshoes.com.sg/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.aldoshoes.com.sg/pages/beware-of-fraud, which answers with an error. Visitors hit a dead end and search engines drop it.
5 pages without a meta description
https://www.aldoshoes.com.sg/pages/store-locator, https://www.aldoshoes.com.sg/pages/faq, https://www.aldoshoes.com.sg/collections/9-9-mega-deals, https://www.aldoshoes.com.sg/pages/aldo-artist-series and https://www.aldoshoes.com.sg/pages/butterlux have no meta description, so Google writes the search snippet from whatever text it finds.
14 pages without an H1
https://www.aldoshoes.com.sg/collections/all, https://www.aldoshoes.com.sg/pages/store-locator, https://www.aldoshoes.com.sg/pages/faq, https://www.aldoshoes.com.sg/collections/9-9-mega-deals, https://www.aldoshoes.com.sg/pages/aldo-artist-series and https://www.aldoshoes.com.sg/pages/butterlux and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://www.aldoshoes.com.sg/collections/all, https://www.aldoshoes.com.sg/collections/9-9-mega-deals and https://www.aldoshoes.com.sg/collections/new-arrivals-women-footwear 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.
3 pages slow to respond
https://www.aldoshoes.com.sg/pages/store-locator, https://www.aldoshoes.com.sg/pages/faq and https://www.aldoshoes.com.sg/collections/9-9-mega-deals took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 126 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.
2 checks passed
Tap targets are thumb-sized
93 of 99 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 543 words of copy
The homepage carries about 543 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 the Collection”.
12 calls to action
The homepage has 12 calls to action, for example “Login | Register”, “Track Order” and “Shop the Collection”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo 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.
21 cookies set on arrival
21Opening the homepage sets 21 cookies, 1 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.
34 other companies contacted
Loading the homepage contacts 34 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 aldoshoes.com.sg, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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 47 issues on aldoshoes.com.sg, including 22 speed issues, 5 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.