ehf.org website review

6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

About 385 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 810 ms faster on a phone.

Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.

3 images could be 941 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 610 ms faster on a phone.

5 third-party services load with your homepage (Squarespace, Google CDN and JSDelivr CDN and others), adding 2.1 MB and 523 ms of main-thread time.

Squarespace costs a phone 499 ms of main-thread work and 928 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.

squarespace-cdn.com costs a phone 0 ms of main-thread work and 1.2 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.

2 long tasks block the main thread while loading, the longest for 240 ms. During a long task the page ignores taps.

10 files are served with short cache lifetimes, so returning visitors download them again (193 KiB).

Polyfills for old browsers add 32 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

The first text or image appears after 4.2 s on a phone. Good is under 1.8 s.

The page becomes fully interactive after 9.6 s. Good is under 3.8 s.

Visually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Created to give life to the Global Impact Visa, the Edmund …”. Most of its time is element render delay (2.4 s).

1 image have no width and height attributes, so the layout jumps as each one loads.

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Group+1234.png weighs 601 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.2 MB in 39 requests on a phone: images 1.0 MB (3), scripts 819 KiB (23) and stylesheets 162 KiB (7). Under 2 MB keeps phones on slow connections fast.

By the Sustainable Web Design model, a visit to your homepage emits about 0.61 g of CO₂e: 73.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Headings skip levels (h1 → h3, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.

There are 3 <h1> headlines (“Edmund Hillary Fellowship (EHF) 2016 - 2026”, “EHF - The Organisation” and “The Fellowship”). One clear main headline is easier for people and search engines.

Structured data found (LocalBusiness and WebSite) but with 2 problems, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/5f3874da9e73700975a…”.

The homepage links to 38 pages on ehf.org and 2 external pages.

Your Organization JSON-LD is missing name, url, 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.

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.

Your homepage links to /news, which answers with an error. Visitors hit a dead end and search engines drop it.

/about-ehf and /about all use the title “Unlocking the Potential | Edmund Hillary Fellowship — Edmund Hillary …”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/communitycollective, /ehf-fellows-articles and /fellow-directory-advanced-search have no meta description, so Google writes the search snippet from whatever text it finds.

/about-ehf and /about use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /about, whose canonical is /about-ehf. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/communitycollective, /ehf-fellows-articles, /fellow-directory and /fellow-directory-advanced-search have no <h1> headline, so visitors and search engines get no clear main topic.

/communitycollective, /ehf-fellows-articles, /fellow-directory and /fellow-directory-advanced-search 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.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://static1.squarespace.com/static/versioned-site-css/5f3874da9e73700975a00b12/427/5c5…”.

1 link from your homepage to your own site is broken, for example https://www.ehf.org/news (404).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

HSTS is set, but max-age is 0 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://edmund-hillary-fellowship.squarespace.com/config/?frameUrl=%2Ffellow-directory.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

ehf.org 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.

ehf.org'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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage has only about 243 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

There is no form on the homepage, so every lead has to click through to another page first.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

DMARC is set to p=none, so mail pretending to be ehf.org is still delivered. Add a report address, check the reports, then move to quarantine.

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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.