Website review, no card needed
200lab.io website review
Visit site (opens in a new tab)Reviewed 10 November 202614 issues · 72 checks
This review found 14 issues worth fixing on 200lab.io, 1 of them high impact, across 72 checks. The most urgent: fails Core Web Vitals for real visitors. 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
98AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.4 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.4 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 93 ms |
| May 30, 2026 | 83 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 82 ms |
| Jun 20, 2026 | 82 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 93 ms |
| Jul 11, 2026 | 81 ms |
| Jul 18, 2026 | 72 ms |
| Jul 25, 2026 | 69 ms |
| Aug 1, 2026 | 66 ms |
| Aug 8, 2026 | 65 ms |
| Aug 15, 2026 | 70 ms |
| Aug 22, 2026 | 77 ms |
| Aug 29, 2026 | 77 ms |
| Sep 5, 2026 | 84 ms |
| Sep 12, 2026 | 83 ms |
| Sep 19, 2026 | 88 ms |
| Sep 26, 2026 | 95 ms |
| Oct 3, 2026 | 110 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 127 ms |
| Oct 24, 2026 | 127 ms |
| Oct 31, 2026 | 131 ms |
| Nov 7, 2026 | 129 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
Reduce initial server response time
661 msReduce initial server response time. Google estimates savings of 661 ms on a phone.
Document request latency
650 msThe HTML itself could arrive about 650 ms sooner: redirects, a slow server response or missing compression delay everything after it.
1,927 HTML elements
The page has 1,927 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 761 ms
761 msYour server takes 761 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 111 ms. During a long task the page ignores taps.
Improve image delivery
64 KiB4 images could be 64 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need.
Reduce unused JavaScript
22 KiBAbout 22 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
10 KiB6 files are served with short cache lifetimes, so returning visitors download them again (10 KiB).
1 third-party service on the page
1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 9 ms of main-thread time.
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
Mobile performance score: 97
97/100Your mobile performance score is 97. That is in Google's “good” band (90 and up).
Main-thread work: 1.1 s
A phone's processor spends 1.1 s on main-thread work while loading, 526 ms of it running JavaScript. That is comfortably low.
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.
Tap response (INP) got 48% slower for real visitors
+48%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 93 ms to 129 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 970 ms
970 msReal visitors wait 970 ms for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 5.5 s
5.5 sThe page becomes fully interactive after 5.5 s. Good is under 3.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
8 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 128 ms
128 msReal visitors wait 128 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.5 s
1.5 sThe first text or image appears after 1.5 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.009
0.009The layout barely moves while loading (CLS 0.009, good is under 0.1).
Largest Contentful Paint: 1.5 s
1.5 sYour largest element renders in 1.5 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “For developers, vibe coders and anyone new to AI at work: 2…”.
Total Blocking Time: 43 ms
43 msScripts block the page for only 43 ms while loading. Good is under 200 ms.
Images and page weight
About 0.3 g of CO₂ per visit
0.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 33.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1,006 KiB in 69 requests
1,006 KiBYour homepage downloads 1,006 KiB in 69 requests on a phone: scripts 446 KiB (38), fonts 192 KiB (11) and HTML 139 KiB (1). That is a lean page.
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
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 45 images in the HTML carry an alt attribute.
57 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: 57 passed and 0 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
61 internal links, 13 external
The homepage links to 61 pages on 200lab.io and 13 external pages.
8 checks passed
Meta description: 117 characters
Your meta description is 117 characters: “From systems thinking to agents running in production: learn through the very business problems 200Lab has delivered.”.
One H1 headline
Your main headline reads: “Mindset & applied AI for real work”.
Title: 32 characters
Your title is a healthy 32 characters: “Level Up Your AI Skills · 200Lab”.
Canonical URL set
The canonical URL is https://200lab.io/en.
Structured data in place
Structured data found: FAQPage, Organization 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://200lab.io/sitemaps/posts.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 (3,149 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://200lab.io/llms.txt (38 KiB, 100 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://200lab.io/certificates/verify is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://200lab.io/en and / all use the title “Level Up Your AI Skills · 200Lab”. Search engines can't tell which page to show for a search, so each competes with the others.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example /, whose canonical is https://200lab.io/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 23 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
16 of 19 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 885 words of copy
The homepage carries about 885 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Try it free”.
2 calls to action
The homepage has 2 calls to action, for example “Try it free”.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks, 4 customer or partner logos, a star rating, 1 trust badge and “20m Students”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 200lab.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on 200lab.io, including 10 speed issues. 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.