Website review, no card needed
thestempedia.com website review
Visit site (opens in a new tab)Reviewed 22 October 202641 issues · 86 checks
This review found 41 issues worth fixing on thestempedia.com, 17 of them high impact, across 86 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
64D- #109,026 of 115,825 reviewed websitesbeats 5%
- #64,784 of 66,612 online storesbeats 2%
- #2,454 of 2,640 WooCommerce storesbeats 6%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 8.9 s |
| May 9, 2026 | 8.8 s |
| May 16, 2026 | 8.4 s |
| May 23, 2026 | 8.5 s |
| May 30, 2026 | 8.5 s |
| Jun 6, 2026 | 8.2 s |
| Jun 13, 2026 | 8.2 s |
| Jun 20, 2026 | 8.3 s |
| Jun 27, 2026 | 8.5 s |
| Jul 4, 2026 | 8.8 s |
| Jul 11, 2026 | 8.7 s |
| Jul 18, 2026 | 8.5 s |
| Jul 25, 2026 | 8.4 s |
| Aug 1, 2026 | 8.7 s |
| Aug 8, 2026 | 9.2 s |
| Aug 15, 2026 | 10.4 s |
| Aug 22, 2026 | 12.1 s |
| Aug 29, 2026 | 10.0 s |
| Sep 5, 2026 | 8.4 s |
| Sep 12, 2026 | 6.5 s |
| Sep 19, 2026 | 5.6 s |
| Sep 26, 2026 | 5.6 s |
| Oct 3, 2026 | 5.6 s |
| Oct 10, 2026 | 5.7 s |
| Oct 17, 2026 | 5.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 309 ms |
| May 9, 2026 | 312 ms |
| May 16, 2026 | 309 ms |
| May 23, 2026 | 306 ms |
| May 30, 2026 | 303 ms |
| Jun 6, 2026 | 315 ms |
| Jun 13, 2026 | 316 ms |
| Jun 20, 2026 | 316 ms |
| Jun 27, 2026 | 312 ms |
| Jul 4, 2026 | 305 ms |
| Jul 11, 2026 | 311 ms |
| Jul 18, 2026 | 328 ms |
| Jul 25, 2026 | 339 ms |
| Aug 1, 2026 | 343 ms |
| Aug 8, 2026 | 359 ms |
| Aug 15, 2026 | 366 ms |
| Aug 22, 2026 | 373 ms |
| Aug 29, 2026 | 375 ms |
| Sep 5, 2026 | 355 ms |
| Sep 12, 2026 | 350 ms |
| Sep 19, 2026 | 347 ms |
| Sep 26, 2026 | 352 ms |
| Oct 3, 2026 | 360 ms |
| Oct 10, 2026 | 361 ms |
| Oct 17, 2026 | 371 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.7 s
3.0 s
Speed
Use efficient cache lifetimes
6.2 s · 2.2 MB197 files are served with short cache lifetimes, so returning visitors download them again (2.2 MB).
Reduce unused JavaScript
5.3 s · 2.3 MBAbout 2.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.3 s faster on a phone.
Render-blocking requests
2.2 s46 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.2 s.
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 54). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.9 s
A phone's processor spends 6.9 s on main-thread work while loading, 3.7 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 (YouTube, Google Tag Manager and Google CDN and others), adding 4.4 MB and 2.5 s of main-thread time.
YouTube adds 883 ms
883 msYouTube costs a phone 883 ms of main-thread work and 1.9 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.
Reduce unused CSS
750 ms · 276 KiBAbout 276 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 659 ms
659 msGoogle Tag Manager costs a phone 659 ms of main-thread work and 1.1 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.
Google CDN adds 353 ms
353 msGoogle CDN costs a phone 353 ms of main-thread work and 733 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 253 ms
253 msFacebook costs a phone 253 ms of main-thread work and 309 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.
2,831 HTML elements
The page has 2,831 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
252 KiB14 images could be 252 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 178 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 2 KiB2 KiB could be saved by minifying JavaScript.
Legacy JavaScript
50 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 14 ms
14 msYour server sent the HTML in 14 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: 5.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.27
0.27For real visitors the layout shifts by 0.27 (75th percentile). Good is under 0.1.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.7 s
3.7 sReal visitors wait 3.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 40.5 s
40.5 sThe page becomes fully interactive after 40.5 s. Good is under 3.8 s.
Speed Index: 15.0 s
15.0 sVisually, the page fills in at 15.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 5.9 s
5.9 sThe first text or image appears after 5.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user INP: 401 ms
401 msReal visitors wait 401 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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-10-17, real Chrome visitors' tap response (inp) went from 309 ms to 371 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Largest content (LCP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 8.9 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 7.4 MB in 273 requests
7.4 MBYour homepage downloads 7.4 MB in 273 requests on a phone: scripts 4.7 MB (110), images 1.4 MB (62) and stylesheets 409 KiB (57). Under 2 MB keeps phones on slow connections fast.
16 images in older formats
16 images (1.1 MB) are 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.
An image on the first screen is lazy-loaded
Homepage-image0-441x441.png 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).
14 images below the first screen load straight away
14 images further down the page (519 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.09 g of CO₂e: 251.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 are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
28 text elements with low contrast
28 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (39 elements)
All page content should be contained by landmarks: 39 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.
24 links without text
24 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 147 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “STEMpedia | Coding, AI, and Robotics Solutions for Students & Schools”.
Meta description is long (211 characters)
Your meta description is 211 characters; Google truncates after about 160, so the end of your pitch is cut.
178 internal links, 81 external
The homepage links to 178 pages on thestempedia.com and 81 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Next-Gen Learning with STEM, AI, and Robotics!”.
Canonical URL set
The canonical URL is https://thestempedia.com/.
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://thestempedia.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://thestempedia.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: 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 (2,460 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://thestempedia.com/shop has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://thestempedia.com/demo and https://thestempedia.com/product/wizbot have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages slow to respond
https://thestempedia.com/demo, https://thestempedia.com/contact, https://thestempedia.com/shop, https://thestempedia.com/product, https://thestempedia.com/product/pictoblox and https://thestempedia.com/product/quarky-intellio and 6 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 75 found) and read each the way a search engine does.
5 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.
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
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
104 of 113 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
A 16-field form
Your longest form asks for 16 fields (9 required). Every extra field lowers completion.
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,355 words of copy
The homepage carries about 2,355 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” and “SHOP BY CATEGORY”.
14 calls to action
The homepage has 14 calls to action, for example “Book a Demo .a { fill: #FF822E; }”, “Shop .a { fill: #3bbaf0; }” and “Shop”.
Social proof on the page
Social proof on the homepage: a star rating, 10 trust badges and “3M+ Students”.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel, Microsoft Clarity and Cloudflare Web Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
27 other companies contacted
Loading the homepage contacts 27 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 thestempedia.com, 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 Analytics | Microsoft Clarity
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 thestempedia.com, including 25 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.