Website review, no card needed
carbonmapper.org website review
Visit site (opens in a new tab)Reviewed 17 November 202615 issues · 60 checks
This review found 15 issues worth fixing on carbonmapper.org, 3 of them high impact, across 60 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.4 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.2 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.2 s |
| Aug 15, 2026 | 3.3 s |
| Aug 22, 2026 | 3.3 s |
| Aug 29, 2026 | 3.2 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.5 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
| Nov 7, 2026 | 2.4 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 125 ms |
| Jun 6, 2026 | 126 ms |
| Jun 13, 2026 | 123 ms |
| Jun 20, 2026 | 121 ms |
| Jun 27, 2026 | 121 ms |
| Jul 4, 2026 | 114 ms |
| Jul 11, 2026 | 111 ms |
| Jul 18, 2026 | 111 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 112 ms |
| Aug 8, 2026 | 112 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 118 ms |
| Aug 29, 2026 | 112 ms |
| Sep 5, 2026 | 112 ms |
| Sep 12, 2026 | 108 ms |
| Sep 19, 2026 | 105 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 99 ms |
| Oct 10, 2026 | 111 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 110 ms |
| Oct 31, 2026 | 112 ms |
| Nov 7, 2026 | 106 ms |
| Nov 14, 2026 | 105 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
0.5 s
1.0 s
1.4 s
1.9 s
2.4 s
2.9 s
3.4 s
3.9 s
Speed
Reduce unused JavaScript
1.4 s · 397 KiBAbout 397 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.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
1 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 280 KiB and 243 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 239 ms. During a long task the page ignores taps.
Reduce unused CSS
150 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Render-blocking requests
150 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Improve image delivery
15 KiB1 image could be 15 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need.
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.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 704 ms of it running JavaScript. That is comfortably low.
Server response: 19 ms
19 msYour server sent the HTML in 19 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: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Satellite view of Earth's horizon from space”.
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.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.7 s
5.7 sThe page becomes fully interactive after 5.7 s. Good is under 3.8 s.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
Total Blocking Time: 277 ms
277 msScripts block taps and scrolling for 277 ms in total while the page loads. Good is under 200 ms.
7 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 105 ms
105 msReal visitors wait 105 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.
Real-user TTFB: 708 ms
708 msReal visitors wait 708 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 125 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 32% faster for real visitors
-32%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.2 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.34 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.34 g of CO₂e: 41.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.2 MB in 40 requests
1.2 MBYour homepage downloads 1.2 MB in 40 requests on a phone: scripts 919 KiB (26), fonts 156 KiB (4) and images 59 KiB (2). That is a lean page.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
SEO
23 internal links, 11 external
The homepage links to 23 pages on carbonmapper.org and 11 external pages.
8 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Our mission is to drive greenhouse gas emission reductions by making methane and carbon dioxide data accessible and act…”.
One H1 headline
Your main headline reads: “Accelerating local climate action, globally.”.
Title: 65 characters
Your title is a healthy 65 characters: “Methane, CO2 Detection Satellite | Greenhouse Gas | Carbon Mapper”.
Canonical URL set
The canonical URL is https://carbonmapper.org/.
Structured data in place
Structured data found: NonprofitOrganization, Organization 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://carbonmapper.org/sitemap.xml.
AI search readiness
Parts of the site are closed to 1 AI crawler
Your robots.txt lets Perplexity (PerplexityBot) read the homepage but closes other sections to them, so answers about those pages can't cite you.
2 checks passed
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
llms.txt published
The site publishes https://carbonmapper.org/llms.txt (16 KiB, 62 links), a plain-text guide to the site for AI tools.
Other pages
1 page without an H1
https://carbonmapper.org/resources has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://carbonmapper.org/resources took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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.
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
5 console errors
5 errors were logged to the browser console during Google's test (“Connecting to 'https://analytics.google.com/g/collect?v=2&tid=G-X1K552FETB>m=45je6bd1v9170935071z…”).
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 36 testimonial or review blocks. 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 549 words of copy
The homepage carries about 549 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Learn more about our partners”, “Learn more about our impact” and “Learn more through various resources”.
1 short form
A short form (6 fields at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
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 carbonmapper.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Company
- Employees
- 40
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on carbonmapper.org, including 9 speed issues and 2 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.