Website review, no card needed
vegaschool.com website review
Visit site (opens in a new tab)Reviewed 26 October 202646 issues · 89 checks
This review found 46 issues worth fixing on vegaschool.com, 13 of them high impact, across 89 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.1 s |
| May 9, 2026 | 2.1 s |
| May 16, 2026 | 2.2 s |
| May 23, 2026 | 2.2 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.1 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.1 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 395 ms |
| May 9, 2026 | 420 ms |
| May 16, 2026 | 435 ms |
| May 23, 2026 | 412 ms |
| May 30, 2026 | 395 ms |
| Jun 6, 2026 | 385 ms |
| Jun 13, 2026 | 387 ms |
| Jun 20, 2026 | 405 ms |
| Jun 27, 2026 | 429 ms |
| Jul 4, 2026 | 431 ms |
| Jul 11, 2026 | 453 ms |
| Jul 18, 2026 | 506 ms |
| Jul 25, 2026 | 552 ms |
| Aug 1, 2026 | 577 ms |
| Aug 8, 2026 | 570 ms |
| Aug 15, 2026 | 515 ms |
| Aug 22, 2026 | 494 ms |
| Aug 29, 2026 | 506 ms |
| Sep 5, 2026 | 506 ms |
| Sep 12, 2026 | 507 ms |
| Sep 19, 2026 | 493 ms |
| Sep 26, 2026 | 485 ms |
| Oct 3, 2026 | 489 ms |
| Oct 10, 2026 | 489 ms |
| Oct 17, 2026 | 489 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
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, YouTube and Facebook and others), adding 2.3 MB and 1.2 s of main-thread time.
Reduce unused JavaScript
1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page.
Mobile performance score: 74
74/100Your mobile performance score is 74 (desktop: 70). Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
Use efficient cache lifetimes
450 ms · 417 KiB25 files are served with short cache lifetimes, so returning visitors download them again (417 KiB).
Reduce unused CSS
600 ms · 226 KiBAbout 226 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 530 ms
530 msGoogle Tag Manager costs a phone 530 ms of main-thread work and 847 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 959 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.
Improve image delivery
300 ms · 34 KiB3 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 212 ms
212 msFacebook costs a phone 212 ms of main-thread work and 336 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.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 12 KiB12 KiB could be saved by minifying CSS.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 147 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).
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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 FCP: 3.2 s
3.2 sReal visitors see the first content after 3.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 21.1 s
21.1 sThe page becomes fully interactive after 21.1 s. Good is under 3.8 s.
Real-user LCP: 3.7 s
3.7 sReal visitors wait 3.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 323 ms
323 msReal visitors wait 323 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 20% slower for real visitors
+20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 395 ms to 489 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 3.4 s
3.4 sYour largest element takes 3.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Vega School at Emeris prepares graduates to enter indust…”.
Total Blocking Time: 399 ms
399 msScripts block taps and scrolling for 399 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Images and page weight
Page weight: 3.1 MB in 127 requests
3.1 MBYour homepage downloads 3.1 MB in 127 requests on a phone: scripts 2.3 MB (33), images 432 KiB (39) and stylesheets 191 KiB (9). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (171 KiB) 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.
3 images below the first screen load straight away
3 images further down the page (209 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 106.4 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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
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.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
Orphan list items
Some list items are not inside a list.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 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.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h5, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (188 characters)
Your meta description is 188 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links with vague text
6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
146 internal links, 15 external
The homepage links to 146 pages on vegaschool.com and 15 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Vega School at Emeris”.
Title: 55 characters
Your title is a healthy 55 characters: “Faculty of Vega School | Study Design, Brand & Business”.
Canonical URL set
The canonical URL is https://www.emeris.ac.za/faculty/vega-school.
Structured data in place
Structured data found: BreadcrumbList and EducationalOrganization.
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.emeris.ac.za/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.emeris.ac.za/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,269 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.emeris.ac.za/about/faq has no <title>, so Google invents the link text in results.
1 page without a meta description
https://www.emeris.ac.za/about/faq has no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://www.emeris.ac.za/about/quality-assurance-accreditation-regulation, https://www.emeris.ac.za/about/academic-governance and https://www.emeris.ac.za/about/quality-management-system use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.emeris.ac.za/about/faq has no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 92 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.
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.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187246847&tm=gtm002&Ver=2&mid=159d463b-1a09-4453-bd1f-c0ae7cd353f8&bo=1&sid=604f2c40d0e111f1bcf9a37acba2b785&vid=604f64d0d0e111f1b93511b60ad980f9&vids=1&msclkid=N>m_.
20 small tap targets
20 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “$(...).slick is not a function”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 990 words of copy
The homepage carries about 990 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: “Enquire”.
14 calls to action
The homepage has 14 calls to action, for example “Enquire”, “Apply” and “Book a Student Appointment”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 3 mores (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, 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.
23 other companies contacted
Loading the homepage contacts 23 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 vegaschool.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
Company
- Founded
- 1999
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on vegaschool.com, including 22 speed issues, 2 SEO issues 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.