Website review, no card needed
imeche.org website review
Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 89 checks
This review found 46 issues worth fixing on imeche.org, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.5 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.6 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 165 ms |
| May 23, 2026 | 151 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 143 ms |
| Jun 20, 2026 | 146 ms |
| Jun 27, 2026 | 147 ms |
| Jul 4, 2026 | 145 ms |
| Jul 11, 2026 | 144 ms |
| Jul 18, 2026 | 134 ms |
| Jul 25, 2026 | 131 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 137 ms |
| Aug 15, 2026 | 151 ms |
| Aug 22, 2026 | 158 ms |
| Aug 29, 2026 | 152 ms |
| Sep 5, 2026 | 150 ms |
| Sep 12, 2026 | 138 ms |
| Sep 19, 2026 | 135 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 135 ms |
| Oct 10, 2026 | 137 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 145 ms |
| Oct 31, 2026 | 145 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 unused JavaScript
2.6 s · 701 KiBAbout 701 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.6 s faster on a phone.
Render-blocking requests
2.6 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Improve image delivery
550 ms · 3.3 MB14 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google Maps and Google/Doubleclick Ads and others), adding 1.4 MB and 711 ms of main-thread time.
Font display
800 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 800 ms).
Legacy JavaScript
650 ms · 76 KiBPolyfills for old browsers add 76 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 650 ms faster on a phone.
Use efficient cache lifetimes
200 ms · 387 KiB14 files are served with short cache lifetimes, so returning visitors download them again (387 KiB).
Reduce unused CSS
450 ms · 68 KiBAbout 68 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Minify CSS
300 ms · 20 KiB20 KiB could be saved by minifying CSS.
Google Tag Manager adds 256 ms
256 msGoogle Tag Manager costs a phone 256 ms of main-thread work and 329 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.
Google Maps adds 135 ms
135 msGoogle Maps costs a phone 135 ms of main-thread work and 393 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 14 KiB14 KiB could be saved by minifying JavaScript.
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
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 833 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 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.
Largest Contentful Paint: 15.8 s
15.8 sYour largest element takes 15.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Improving the world through engineering Volunteer as a judg…”.
Time to Interactive: 19.9 s
19.9 sThe page becomes fully interactive after 19.9 s. Good is under 3.8 s.
Speed Index: 7.2 s
7.2 sVisually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
Real-user FCP: 2.0 s
2.0 sReal visitors see the first content after 2.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 165 ms to 145 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 113 ms
113 msReal visitors wait 113 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.
Total Blocking Time: 191 ms
191 msScripts block the page for only 191 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.7 MB in 92 requests
5.7 MBYour homepage downloads 5.7 MB in 92 requests on a phone: images 3.8 MB (22), scripts 1.4 MB (28) and other files 200 KiB (27). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
13 images in older formats
13 images (3.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.
8 images below the first screen load straight away
8 images further down the page (3.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 193.3 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
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Links must have discernible text (3 elements)
Links must have discernible text: 3 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
<object> elements must have alternative text (1 element)
<object> elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (21 elements)
All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.
Banner landmark should not be contained in another landmark (4 elements)
Banner landmark should not be contained in another landmark: 4 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
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 social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
109 internal links, 16 external
The homepage links to 109 pages on imeche.org and 16 external pages.
4 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “Institution of Mechanical Engineers - IMechE”.
Canonical URL set
The canonical URL is http://www.imeche.org/.
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://imeche.org/sitemap/sitemap.xml.
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.
No llms.txt
There is no https://www.imeche.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.
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 (756 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://www.imeche.org/careers-education/end-point-assessment has no meta description, so Google writes the search snippet from whatever text it finds.
5 pages share a meta description
https://www.imeche.org/membership-registration, https://www.imeche.org/membership-registration/membership-partner and https://www.imeche.org/membership-registration/help-with-your-application use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 76 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
19 small tap targets
19 of 41 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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 call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: “over 110,000 members”. Pairing it with named testimonials or customer logos makes it far more convincing.
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 745 words of copy
The homepage carries about 745 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Find out how to join us” and “Request a Training catalogue”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and LinkedIn Insight (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
19 other companies contacted
Loading the homepage contacts 19 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 imeche.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Sitefinity 12.2.7200.0 PU
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Azure
Hiring
- Hiring
- 1 open role
- Job board
- careers page
Company
- Employees
- 222
- Founded
- 1847
- Headquarters
- London
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 imeche.org, including 20 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.