Website review, no card needed
icef.com website review
Visit site (opens in a new tab)Reviewed 3 November 202632 issues · 94 checks
This review found 32 issues worth fixing on icef.com, 14 of them high impact, across 94 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 5.0 s |
| May 23, 2026 | 5.0 s |
| May 30, 2026 | 4.9 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.8 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.8 s |
| Jul 11, 2026 | 4.8 s |
| Jul 18, 2026 | 4.7 s |
| Jul 25, 2026 | 4.6 s |
| Aug 1, 2026 | 4.5 s |
| Aug 8, 2026 | 4.4 s |
| Aug 15, 2026 | 4.4 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.9 s |
| Sep 12, 2026 | 5.0 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.6 s |
| Oct 3, 2026 | 4.7 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 5.1 s |
| Oct 31, 2026 | 5.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 154 ms |
| May 23, 2026 | 159 ms |
| May 30, 2026 | 153 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 151 ms |
| Jun 20, 2026 | 145 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 148 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 156 ms |
| Aug 8, 2026 | 150 ms |
| Aug 15, 2026 | 154 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 148 ms |
| Sep 12, 2026 | 156 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 207 ms |
| Oct 3, 2026 | 215 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 198 ms |
| Oct 24, 2026 | 180 ms |
| Oct 31, 2026 | 182 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
1.7 s · 294 KiBAbout 294 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Render-blocking requests
1.9 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Usercentrics CMP and privasee.io and others), adding 850 KiB and 686 ms of main-thread time.
Google Tag Manager adds 445 ms
445 msGoogle Tag Manager costs a phone 445 ms of main-thread work and 453 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.
Usercentrics CMP adds 232 ms
232 msUsercentrics CMP costs a phone 232 ms of main-thread work and 340 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.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 200 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
150 ms · 21 KiB3 files are served with short cache lifetimes, so returning visitors download them again (21 KiB).
Legacy JavaScript
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
6 KiB6 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, 971 ms of it running JavaScript. That is comfortably low.
Server response: 115 ms
115 msYour server sent the HTML in 115 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: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 8.8 s
8.8 sYour largest element takes 8.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We would like to offer you a comfortable use of our website…”. Most of its time is element render delay (4.1 s).
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 8.9 s
8.9 sThe page becomes fully interactive after 8.9 s. Good is under 3.8 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.4 s
1.4 sReal visitors wait 1.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 302 ms
302 msScripts block taps and scrolling for 302 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 154 ms to 182 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 5.0 s to 5.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.3 g of CO₂ per visit
0.28 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.28 g of CO₂e: 34.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 1,023 KiB in 56 requests
1,023 KiBYour homepage downloads 1,023 KiB in 56 requests on a phone: scripts 817 KiB (27), other files 125 KiB (13) and fonts 43 KiB (5). That is a lean page.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (20 elements)
All page content should be contained by landmarks: 20 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 checks passed
Every image has alt text
All 11 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. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
101 internal links, 15 external
The homepage links to 101 pages on icef.com and 15 external pages.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “ICEF is a global organisation serving international education through events, quality frameworks, market intelligence, …”.
One H1 headline
Your main headline reads: “ICEF”.
Title: 36 characters
Your title is a healthy 36 characters: “ICEF: Home - Connect. Recruit. Grow.”.
Canonical URL set
The canonical URL is https://www.icef.com/.
Structured data in place
Structured data found: BreadcrumbList, Corporation, WebPage and WebSite.
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.icef.com/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, logo, sameAs (social profiles) and description. 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 /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 (667 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page hidden from search
/events/icef-canada is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 68 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
65 small tap targets
65 of 77 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: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
No HSTS header
No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
HTTP/1.1 only
The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
1 link through redirect chains
1 link go through two or more redirects, for example https://instagram.com/icefglobal.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
4 checks passed
Served over HTTPS
The homepage is served over HTTPS (icef.com).
Valid certificate (78 days left)
The certificate from Let's Encrypt · YE1 verifies for icef.com and is valid for another 78 days.
http:// redirects to https
http://icef.com redirects to the secure version.
All 47 links work
All 47 links checked from your homepage (40 internal, 7 external) answered without errors.
Domain and trust
Domain expires in 87 days
icef.com is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.
No CAA record
icef.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
icef.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
1 checks passed
Domain is 28 years old
28 yearsicef.com was registered in Jan 1998 through INWX GmbH. An established domain carries more trust with email providers and search engines.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 566 words of copy
The homepage carries about 566 words of visible text.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
Analytics in place
Analytics detected: Google Tag Manager.
Email authentication
DMARC is monitor-only (p=none)
DMARC is set to p=none, so mail pretending to be icef.com is still delivered. Reports are on, so moving to quarantine is the next step.
Email authentication score: 70/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
2 checks passed
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 ip4:13.111.0.0/16 ip4:20.62.181.248/29 ip4:20.77.87.163 ip4:20.85.181.240/29 ip4:20.121.230.0/29 ip4:20.185.226.…”.
DKIM signing found
A DKIM key is published (selector “google”, “k1” and “s1”), so receivers can verify mail really came from you.
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). A consent tool (Usercentrics) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Usercentrics
A consent management tool (Usercentrics) loads with the page.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- WordPress 7.1.4
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- OVHcloud
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on icef.com, including 15 speed issues, 1 SEO issue 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.