Website review, no card needed
mindchamps.org website review
Visit site (opens in a new tab)Reviewed 30 October 202641 issues · 90 checks
This review found 41 issues worth fixing on mindchamps.org, 17 of them high impact, across 90 checks. The most urgent: use efficient cache lifetimes. 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- #93,653 of 115,512 reviewed websitesbeats 16%
- #58,427 of 66,521 online storesbeats 10%
- #1,896 of 2,635 WooCommerce storesbeats 24%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 3.8 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.8 s |
| Jul 25, 2026 | 3.9 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 4.0 s |
| Sep 5, 2026 | 4.2 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.4 s |
| Sep 26, 2026 | 4.5 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.6 s |
| Oct 24, 2026 | 4.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 155 ms |
| May 16, 2026 | 153 ms |
| May 23, 2026 | 146 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 151 ms |
| Jun 13, 2026 | 155 ms |
| Jun 20, 2026 | 162 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 156 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 150 ms |
| Aug 8, 2026 | 152 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 169 ms |
| Sep 5, 2026 | 170 ms |
| Sep 12, 2026 | 170 ms |
| Sep 19, 2026 | 163 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 106 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
0.8 s
1.7 s
2.5 s
3.3 s
4.2 s
5.0 s
5.9 s
6.7 s
Speed
Use efficient cache lifetimes
3.1 s · 641 KiB60 files are served with short cache lifetimes, so returning visitors download them again (641 KiB).
Reduce unused JavaScript
2.4 s · 281 KiBAbout 281 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.
Render-blocking requests
1.6 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3,097 HTML elements
The page has 3,097 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 Cloudflare CDN and others), adding 5.1 MB and 756 ms of main-thread time.
Reduce unused CSS
450 ms · 132 KiBAbout 132 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Google Tag Manager adds 515 ms
515 msGoogle Tag Manager costs a phone 515 ms of main-thread work and 516 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.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 4.2 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 277 ms. During a long task the page ignores taps.
Improve image delivery
267 KiB8 images could be 267 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 901 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 16 KiB16 KiB could be saved by minifying CSS.
Minify JavaScript
150 ms · 6 KiB6 KiB could be saved by minifying JavaScript.
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 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.
1 checks passed
Server response: 212 ms
212 msYour server sent the HTML in 212 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 LCP: 7.0 s
7.0 sReal visitors wait 7.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.9 s
5.9 sReal visitors see the first content after 5.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 4.3 s
4.3 sReal visitors wait 4.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 11.6 s
11.6 sYour largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “MindChamps makes history by attaining Patent Status in 4 ma…”. Most of its time is element render delay (6.0 s).
Speed Index: 11.6 s
11.6 sVisually, the page fills in at 11.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.406
0.406The layout shifts by 0.406 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
Total Blocking Time: 462 ms
462 msScripts block taps and scrolling for 462 ms in total while the page loads. 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.
18 images without width and height
18 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 141 ms
141 msReal visitors wait 141 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 155 ms to 106 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.6 MB in 103 requests
5.6 MBYour homepage downloads 5.6 MB in 103 requests on a phone: media 3.7 MB (2), scripts 943 KiB (41) and images 524 KiB (19). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
57 KiB2 images are downloaded at several times the size a phone draws them, for example Marina-Square-MC_085-1.webp at 1,280 px wide, shown at 331 px. Resized copies would save about 57 KiB.
1 image in older formats
1 image (63 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 1.6 g of CO₂ per visit
1.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Hidden but focusable
18 elements hidden from screen readers can still receive keyboard focus.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 102 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“MindChamps: The Industry Leader in Early Childhoo…” and “MindChamps: The Industry Leader in Early Educatio…”). One clear main headline is easier for people and search engines.
15 links with vague text
15 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
140 internal links, 40 external
The homepage links to 140 pages on mindchamps.org and 40 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “MindChamps’ 3-Mind Approach offers your children the early childhood education they need. Find out more about our curri…”.
Title: 62 characters
Your title is a healthy 62 characters: “Early Childhood & Development Education Singapore | MindChamps”.
Canonical URL set
The canonical URL is https://www.mindchamps.org/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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.mindchamps.org/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.mindchamps.org/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: 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,809 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
https://www.mindchamps.org/privileges, https://www.mindchamps.org/ph, https://www.mindchamps.org/my and https://www.mindchamps.org/id have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages slow to respond
https://www.mindchamps.org/contact-us, https://www.mindchamps.org/location, https://www.mindchamps.org/shop, https://www.mindchamps.org/privileges, https://www.mindchamps.org/the-mindchamps-story and https://www.mindchamps.org/the-mindchamps-story/founders-note and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 79 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.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
42 of 49 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
A 46-field form
Your longest form asks for 46 fields (29 required). Every extra field lowers completion.
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,861 words of copy
The homepage carries about 1,861 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “SHOP”.
25 calls to action
The homepage has 25 calls to action, for example “CONTACT US”, “SHOP” and “Book a Visit”.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks and “over 100,000 students”.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 3 phone links and 0 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
16 cookies set on arrival
16Opening the homepage sets 16 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.
13 other companies contacted
Loading the homepage contacts 13 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 mindchamps.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on mindchamps.org, including 24 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.