Website review, no card needed
successatschool.org website review
Visit site (opens in a new tab)Reviewed 21 November 202638 issues · 84 checks
This review found 38 issues worth fixing on successatschool.org, 6 of them high impact, across 84 checks. The most urgent: 9 tap targets too small. 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
85BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.4 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.6 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.4 s |
| Nov 7, 2026 | 1.3 s |
| Nov 14, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 148 ms |
| Jun 6, 2026 | 148 ms |
| Jun 13, 2026 | 152 ms |
| Jun 20, 2026 | 150 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 150 ms |
| Jul 11, 2026 | 146 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 127 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 134 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 151 ms |
| Aug 29, 2026 | 151 ms |
| Sep 5, 2026 | 129 ms |
| Sep 12, 2026 | 136 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 129 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 142 ms |
| Oct 24, 2026 | 139 ms |
| Oct 31, 2026 | 139 ms |
| Nov 7, 2026 | 125 ms |
| Nov 14, 2026 | 115 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.6 s
3.0 s
Speed
Use efficient cache lifetimes
1.4 MB9 files are served with short cache lifetimes, so returning visitors download them again (1.4 MB).
Improve image delivery
1.4 MB11 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 294 ms. During a long task the page ignores taps.
3 third-party services on the page
3 third-party services load with your homepage (Google Tag Manager, Google Analytics and Amazon Web Services), adding 1.6 MB and 108 ms of main-thread time.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Amazon Web Services adds 0 ms
0 msAmazon Web Services costs a phone 0 ms of main-thread work and 1.4 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.
Render-blocking requests
250 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 250 ms.
Reduce unused JavaScript
238 KiBAbout 238 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
30 KiBAbout 30 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 97 ms
97 msYour server sent the HTML in 97 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 14.1 s
14.1 sThe page becomes fully interactive after 14.1 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 559 ms
559 msScripts block taps and scrolling for 559 ms in total while the page loads. Good is under 200 ms.
19 images without width and height
19 images have no width and height attributes, so the layout jumps as each one loads.
11 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 119 ms
119 msReal visitors wait 119 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.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 617 ms
617 msReal visitors wait 617 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 19% faster for real visitors
-19%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 148 ms to 115 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 2.0 s
2.0 sYour largest element renders in 2.0 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image.
Cumulative Layout Shift: 0.015
0.015The layout barely moves while loading (CLS 0.015, good is under 0.1).
First Contentful Paint: 1.0 s
1.0 sThe first text or image appears after 1.0 s, inside the 1.8 s “good” threshold.
Images and page weight
9 images far larger than shown
1.2 MB9 images are downloaded at several times the size a phone draws them, for example thumb_101_115-407714699376.png at 1,080 px wide, shown at 145 px. Resized copies would save about 1.2 MB.
Page weight: 3.0 MB in 54 requests
3.0 MBYour homepage downloads 3.0 MB in 54 requests on a phone: images 1.6 MB (24), scripts 705 KiB (15) and other files 522 KiB (9). Under 2 MB keeps phones on slow connections fast.
9 images in older formats
9 images (1.4 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.
9 images below the first screen load straight away
9 images further down the page (1.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
image 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).
About 0.8 g of CO₂ per visit
0.85 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.85 g of CO₂e: 101.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
Links must have discernible text (5 elements)
Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 17 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 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
5 H1 headlines
There are 5 <h1> headlines (“Explore your future”, “Mentoring Zone” and “Top Jobs”). One clear main headline is easier for people and search engines.
Meta description is long (172 characters)
Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://successatschool.org/sitemap.xml, so Google discovers your pages only by following links.
4 links with vague text
4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
Open Graph partly set
Open Graph is missing og:title, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
28 internal links, 11 external
The homepage links to 28 pages on successatschool.org and 11 external pages.
4 checks passed
Title: 58 characters
Your title is a healthy 58 characters: “Success at School: Careers advice for schools and students”.
Canonical URL set
The canonical URL is https://successatschool.org/.
Structured data in place
Structured data found: BreadcrumbList.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
Some text only appears after JavaScript runs
46%The HTML your server sends has 277 of the 602 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
No llms.txt
There is no https://successatschool.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.
1 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.
Other pages
2 pages share a title
/ and https://successatschool.org/mentoring all use the title “Success at School: Careers advice for schools and students”. Search engines can't tell which page to show for a search, so each competes with the others.
8 pages without a meta description
https://successatschool.org/page/employers, https://successatschool.org/page/university, https://successatschool.org/contactus, https://successatschool.org/page/aboutus, https://successatschool.org/page/faq and https://successatschool.org/page/whoarewe and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.
7 pages share a meta description
https://successatschool.org/jobs, https://successatschool.org/career-zones, https://successatschool.org/advice, https://successatschool.org/employers, https://successatschool.org/universities and https://successatschool.org/news and 1 other use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://successatschool.org/contactus, whose canonical is https://successatschool.org/page/contactus. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://successatschool.org/mentoring has no <h1> headline, so visitors and search engines get no clear main topic.
7 pages with very little text
https://successatschool.org/jobs, https://successatschool.org/career-zones, https://successatschool.org/advice, https://successatschool.org/employers, https://successatschool.org/universities and https://successatschool.org/news and 1 other 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.
1 page slow to respond
https://successatschool.org/page/whoarewe took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
14 small tap targets
14 of 63 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
11 distorted images
11 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 6 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 602 words of copy
The homepage carries about 602 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Signup”.
4 calls to action
The homepage has 4 calls to action, for example “Signup”, “Get in touch” and “Contact”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
4 other companies contacted
Loading the homepage contacts 4 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 successatschool.org, 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
- AWS
Company
- Headquarters
- London
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on successatschool.org, including 11 speed issues, 4 SEO issues and 3 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.