Website review, no card needed
etacollege.com website review
Visit site (opens in a new tab)Reviewed 4 November 202630 issues · 81 checks
This review found 30 issues worth fixing on etacollege.com, 11 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
81B- #41,736 of 125,230 reviewed websitesbeats 61%
- #27,565 of 70,135 online storesbeats 54%
- #553 of 2,941 WooCommerce storesbeats 77%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 5.3 s |
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.4 s |
| Jun 13, 2026 | 5.4 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.6 s |
| Jul 18, 2026 | 5.7 s |
| Jul 25, 2026 | 5.6 s |
| Aug 1, 2026 | 5.7 s |
| Aug 8, 2026 | 5.4 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.4 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.4 s |
| Sep 12, 2026 | 5.3 s |
| Sep 19, 2026 | 5.1 s |
| Sep 26, 2026 | 5.2 s |
| Oct 3, 2026 | 5.4 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.6 s |
| Oct 24, 2026 | 5.5 s |
| Oct 31, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 190 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 215 ms |
| Jun 6, 2026 | 217 ms |
| Jun 13, 2026 | 201 ms |
| Jun 20, 2026 | 192 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 180 ms |
| Jul 11, 2026 | 190 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 189 ms |
| Aug 1, 2026 | 194 ms |
| Aug 8, 2026 | 191 ms |
| Aug 15, 2026 | 190 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 192 ms |
| Sep 5, 2026 | 185 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 174 ms |
| Sep 26, 2026 | 172 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 179 ms |
| Oct 17, 2026 | 190 ms |
| Oct 24, 2026 | 192 ms |
| Oct 31, 2026 | 212 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
1.3 s
2.6 s
4.0 s
5.3 s
6.6 s
7.9 s
9.2 s
10.6 s
Speed
Render-blocking requests
3.5 s38 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 85
85/100Your mobile performance score is 85. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
400 ms · 205 KiB7 images could be 205 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Reduce unused JavaScript
544 KiBAbout 544 KiB of JavaScript is downloaded but never used on this page.
Reduce unused CSS
300 ms · 75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,947 HTML elements
The page has 1,947 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 4 KiB4 KiB could be saved by minifying CSS.
Minify JavaScript
153 KiB153 KiB could be saved by minifying JavaScript.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 105 ms. During a long task the page ignores taps.
2 third-party services on the page
2 third-party services load with your homepage (Amazon Web Services and cdn-cookieyes.com), adding 146 KiB and 40 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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 264 ms of it running JavaScript. That is comfortably low.
Server response: 258 ms
258 msYour server sent the HTML in 258 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: 6.2 s
6.2 sReal visitors wait 6.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.6 s
5.6 sReal visitors see the first content after 5.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 14.1 s
14.1 sVisually, the page fills in at 14.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 305 ms
305 msReal visitors wait 305 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
41 images without width and height
41 images have no width and height attributes, so the layout jumps as each one loads.
Largest Contentful Paint: 2.9 s
2.9 sYour largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your leading sports science, sports coaching & sports manag…”. Most of its time is element render delay (9.3 s).
Tap response (INP) held steady for real visitors
+1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 190 ms to 212 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.0 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Time to Interactive: 2.9 s
2.9 sThe page is fully interactive after 2.9 s.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.1 MB in 117 requests
4.1 MBYour homepage downloads 4.1 MB in 117 requests on a phone: images 2.9 MB (25), scripts 603 KiB (33) and fonts 414 KiB (9). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.0 MB together. On a phone connection a single image that size takes seconds.
7 images far larger than shown
559 KiB7 images are downloaded at several times the size a phone draws them, for example Biokinetics.png at 1,200 px wide, shown at 370 px. Resized copies would save about 559 KiB.
11 images in older formats
11 images (2.5 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.
10 images below the first screen load straight away
10 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.16 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.16 g of CO₂e: 139.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 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 (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 49 images in the HTML carry an alt attribute.
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
197 internal links, 144 external
The homepage links to 197 pages on etacollege.com and 144 external pages.
8 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “LAUNCH YOUR CAREER Your leading sports science, sports coaching & sports management institution Personal training, fitn…”.
One H1 headline
Your main headline reads: “Your leading sports science, sports coaching & sports management institution”.
Title: 62 characters
Your title is a healthy 62 characters: “eta College - Sports Science Courses. Register - Get Qualified”.
Canonical URL set
The canonical URL is https://etacollege.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://etacollege.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing 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://etacollege.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.
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,654 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://etacollege.com/post-graduate-diploma-in-sports-performance and https://etacollege.com/bachelor-of-exercise-sports-science all use the title “eta College: Bachelor of Exercise: Sport Science”. Search engines can't tell which page to show for a search, so each competes with the others.
10 pages slow to respond
https://etacollege.com/bachelor-of-exercise-sports-science, https://etacollege.com/advanced-certificate-sport-conditioning, https://etacollege.com/diploma-in-sport-and-exercise, https://etacollege.com/advanced-certificate-in-fitness-sport-conditioning-dl, https://etacollege.com/bachelor-of-sport-and-leisure-management and https://etacollege.com/diploma-sport-and-recreation-management and 4 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 77 found) and read each the way a search engine does.
6 checks passed
Linked pages load
11 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 11 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
68 small tap targets
68 of 115 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 726 words of copy
The homepage carries about 726 words of visible text.
6 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 “Contact”, “Enquire Now” and “Enquire”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 24 customer or partner logos and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
2 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 etacollege.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
- Hosting
- Xneelo
Company
- Founded
- 1983
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on etacollege.com, including 15 speed issues and 1 SEO issue. 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.