Website review, no card needed
nearpod.com website review
Visit site (opens in a new tab)Reviewed 11 October 202623 issues · 75 checks
This review found 23 issues worth fixing on nearpod.com, 3 of them high impact, across 75 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
86BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 18, 2026 | 5.7 s |
| Apr 25, 2026 | 5.8 s |
| May 2, 2026 | 5.9 s |
| May 9, 2026 | 6.1 s |
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.2 s |
| May 30, 2026 | 6.2 s |
| Jun 6, 2026 | 6.2 s |
| Jun 13, 2026 | 6.2 s |
| Jun 20, 2026 | 6.2 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.3 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.3 s |
| Jul 25, 2026 | 6.5 s |
| Aug 1, 2026 | 6.7 s |
| Aug 8, 2026 | 6.7 s |
| Aug 15, 2026 | 6.7 s |
| Aug 22, 2026 | 6.4 s |
| Aug 29, 2026 | 6.2 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 6.0 s |
| Sep 19, 2026 | 6.0 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 6.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 18, 2026 | 198 ms |
| Apr 25, 2026 | 201 ms |
| May 2, 2026 | 202 ms |
| May 9, 2026 | 204 ms |
| May 16, 2026 | 207 ms |
| May 23, 2026 | 204 ms |
| May 30, 2026 | 199 ms |
| Jun 6, 2026 | 194 ms |
| Jun 13, 2026 | 188 ms |
| Jun 20, 2026 | 187 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 187 ms |
| Jul 11, 2026 | 184 ms |
| Jul 18, 2026 | 180 ms |
| Jul 25, 2026 | 211 ms |
| Aug 1, 2026 | 252 ms |
| Aug 8, 2026 | 261 ms |
| Aug 15, 2026 | 253 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 184 ms |
| Sep 5, 2026 | 173 ms |
| Sep 12, 2026 | 174 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 178 ms |
| Oct 3, 2026 | 215 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
8 third-party services on the page
8 third-party services load with your homepage (Unpkg, YouTube and Google Tag Manager and others), adding 1.4 MB and 979 ms of main-thread time.
Reduce unused JavaScript
701 KiBAbout 701 KiB of JavaScript is downloaded but never used on this page.
Unpkg adds 519 ms
519 msUnpkg costs a phone 519 ms of main-thread work and 88 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.
YouTube adds 303 ms
303 msYouTube costs a phone 303 ms of main-thread work and 990 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,810 HTML elements
The page has 2,810 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
150 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Reduce unused CSS
129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 93 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Use efficient cache lifetimes
31 KiB1 file is served with short cache lifetimes, so returning visitors download them again (31 KiB).
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.
2 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92 (desktop: 81). That is in Google's “good” band (90 and up).
Server response: 3 ms
3 msYour server sent the HTML in 3 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: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 201 ms
201 msReal visitors wait 201 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 855 ms
855 msReal visitors wait 855 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Speed Index: 3.8 s
3.8 sVisually, the page fills in at 3.8 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Foster a love of learning in every student”.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' tap response (inp) went from 198 ms to 215 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+7%Over the last 25 four-week periods to 2026-10-03, real Chrome visitors' largest content (lcp) went from 5.7 s to 6.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Total Blocking Time: 62 ms
62 msScripts block the page for only 62 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.6 MB in 60 requests
8.6 MBYour homepage downloads 8.6 MB in 60 requests on a phone: media 6.1 MB (3), scripts 1.3 MB (17) and other files 849 KiB (16). Under 2 MB keeps phones on slow connections fast.
About 2.4 g of CO₂ per visit
2.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.43 g of CO₂e: 291.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
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.
2 checks passed
Every image has alt text
All 44 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
45 internal links, 17 external
The homepage links to 45 pages on nearpod.com and 17 external pages.
7 checks passed
Meta description: 71 characters
Your meta description is 71 characters: “Create active learning experiences students can’t wait to be a part of.”.
One H1 headline
Your main headline reads: “Foster a love of learning in every student”.
Title: 51 characters
Your title is a healthy 51 characters: “Nearpod: Foster a love of learning in every student”.
Structured data in place
Structured data found: Organization, SoftwareApplication 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://nearpod.com/sitemap.xml.
AI search readiness
Opted out of AI training for 1 crawler
robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.
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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (842 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://nearpod.com/llms.txt (2 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://nearpod.com/t/market/init and https://nearpod.com/student all use the title “Nearpod”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://nearpod.com/t/market/init and https://nearpod.com/student have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://nearpod.com/t/market/init and https://nearpod.com/student have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://nearpod.com/blog took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
28 of 30 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 636 words of copy
The homepage carries about 636 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: “Join Lesson” and “Pricing”.
9 calls to action
The homepage has 9 calls to action, for example “Pricing”, “Join lesson” and “Request a quote”.
Social proof on the page
Social proof on the homepage: 16 testimonial or review blocks and 5 customer or partner logos.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 1 of them by other companies (measured from a US location before any click).
32 other companies contacted
Loading the homepage contacts 32 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
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 nearpod.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on nearpod.com, including 15 speed issues, 1 SEO issue and 1 conversion gap. 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.