justonetree.life website review

17 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.4 s faster on a phone.

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

About 264 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.4 s faster on a phone.

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

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

Weebly costs a phone 271 ms of main-thread work and 513 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.

4 third-party services load with your homepage (Weebly, Google Tag Manager and weebly.com and others), adding 693 KiB and 422 ms of main-thread time.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

About 28 KiB of CSS is downloaded but never applied on this page.

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

8 KiB could be saved by minifying JavaScript.

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

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “LET'S PLANT TREES £1 - PLANTS 1 TREE PLANT A TREE HERE”.

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

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 6.3 MB in 83 requests on a phone: images 5.4 MB (48), scripts 630 KiB (12) and fonts 170 KiB (10). Under 2 MB keeps phones on slow connections fast.

22 images further down the page (1.9 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

15 images (1.8 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 are downloaded at several times the size a phone draws them, for example istock-533716420.jpg at 1,098 px wide, shown at 350 px. Resized copies would save about 112 KiB.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

All page content should be contained by landmarks: 21 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is 78 characters, so Google will cut it off around 60: “JUST ONE Tree - £1 plants 1 Tree. Combat Climate Change through reforestation.”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

Your meta description is 255 characters; Google truncates after about 160, so the end of your pitch is cut.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 90 pages on justonetree.life and 14 external pages.

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.

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.

/about-us.html, /why-plant-trees.html, /meet-the-team.html, /our-impact-2026.html, /reforestation-business-collective.html and /reforestation-schools-network.html and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

1 link from your homepage to your own site is broken, for example https://www.justonetree.life/cdn-cgi/l/email-protection (404).

http://justonetree.life does not redirect to https, so some visitors land on the insecure version.

1 link to other sites is dead, for example https://sewfonline.com/about/about-social-enterprise/sewf-verification/ (404).

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

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.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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.

justonetree.life 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.

justonetree.life'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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

The homepage carries about 501 words of visible text.

DMARC is set to p=none, so mail pretending to be justonetree.life 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.

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

Opening the homepage sets 5 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.