Website review, no card needed

climateview.global logo

climateview.global website review

Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 77 checks

This review found 32 issues worth fixing on climateview.global, 10 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of climateview.global (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. climateview.global at 0.4 s0.4 s
  2. climateview.global at 0.8 s0.8 s
  3. climateview.global at 1.1 s1.1 s
  4. climateview.global at 1.5 s1.5 s
  5. climateview.global at 1.9 s1.9 s
  6. climateview.global at 2.3 s2.3 s
  7. climateview.global at 2.6 s2.6 s
  8. climateview.global at 3.0 s3.0 s

Speed

7 to fix57
  • Use efficient cache lifetimes

    3.0 s · 501 KiB

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

  • Reduce unused JavaScript

    2.1 s · 454 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Hubspot, ldnfrpl.com and leadinfo.net and others), adding 20.2 MB and 450 ms of main-thread time.

  • sanity.io adds 0 ms

    0 ms

    sanity.io costs a phone 0 ms of main-thread work and 19.4 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.

  • Improve image delivery

    1.1 MB

    14 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 57

    57/100

    Your mobile performance score is 57 (desktop: 52). Pages that score under 90 lose visitors before the first paint.

  • Hubspot adds 379 ms

    379 ms

    Hubspot costs a phone 379 ms of main-thread work and 552 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.

  • Legacy JavaScript

    150 ms · 58 KiB

    Polyfills for old browsers add 58 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Render-blocking requests

    150 ms

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

  • 7 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Reduce unused CSS

    10 ms · 10 KiB

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

  • 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.7 s

    A phone's processor spends 1.7 s on main-thread work while loading, 1.0 s of it running JavaScript. That is comfortably low.

  • Server response: 40 ms

    40 ms

    Your server sent the HTML in 40 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix65
  • Largest Contentful Paint: 10.9 s

    10.9 s

    Your largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 6.2 s

    6.2 s

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

  • Time to Interactive: 12.5 s

    12.5 s

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

  • Speed Index: 7.3 s

    7.3 s

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

  • 5 images without width and height

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

  • Not enough real-visitor data yet

    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.

2 checks passed
  • Total Blocking Time: 129 ms

    129 ms

    Scripts block the page for only 129 ms while loading. Good is under 200 ms.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

4 to fix43
  • Page weight: 21.0 MB in 98 requests

    21.0 MB

    Your homepage downloads 21.0 MB in 98 requests on a phone: media 18.5 MB (5), images 1.4 MB (25) and scripts 978 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (783 KiB) 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.

  • 3 images below the first screen load straight away

    3 images further down the page (757 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    256 KiB

    1 image is downloaded at several times the size a phone draws it, for example 52cd09314efedb0d674bf84445ff61a4df4cd508-3737x1963.png at 3,737 px wide, shown at 300 px. Resized copies would save about 256 KiB.

  • About 6.0 g of CO₂ per visit

    5.95 g

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

Accessibility

5 to fixGoogle 8792
  • 4 text elements with low contrast

    4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • All page content should be contained by landmarks (2 elements)

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

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 34 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 10080
  • Title is short (23 characters)

    Your title is only 23 characters: “Transition intelligence”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • 4 H1 headlines

    There are 4 <h1> headlines (“ClimateView co-deliver city workshop in Kaohsiung”, “Exploring the next era of climate communication” and “ClimateView supports testbed for Austrian pioneer…”). One clear main headline is easier for people and search engines.

  • No XML sitemap

    No XML sitemap at https://www.climateview.global/sitemap.xml, so Google discovers your pages only by following links.

  • 46 internal links, 9 external

    The homepage links to 46 pages on climateview.global and 9 external pages.

4 checks passed
  • Meta description: 128 characters

    Your meta description is 128 characters: “ClimateView designs technology that helps helps local governments plan, implement, and monitor their sustainability tra…”.

  • Canonical URL set

    The canonical URL is https://www.climateview.global/en.

  • 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.

AI search readiness

1 to fix88
  • 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.climateview.global/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 (381 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 6 pages share 2 titles

    https://www.climateview.global/us/platform and https://www.climateview.global/en/platform all use the title “Platform | ClimateView”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages share a meta description

    https://www.climateview.global/us/approach, https://www.climateview.global/us/platform, https://www.climateview.global/us/clearpath-2.0, https://www.climateview.global/us/opensource, https://www.climateview.global/us/solutions and https://www.climateview.global/us/cases and 9 others 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 22 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.

  • 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

1 to fixGoogle 9693
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    29 of 36 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix79
  • Local business without LocalBusiness data

    Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

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

  • 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 opening hours

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

  • 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 409 words of copy

    The homepage carries about 409 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact”.

  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact”, “Get started” and “Subscribe”.

  • Social proof on the page

    Social proof on the homepage: 7 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: HubSpot.

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads HubSpot (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies, 2 of them by other companies (measured from a US location before any click).

  • 30 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) loads with the page.

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 climateview.global, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
HubSpot CMS
Framework
Next.js
Hosting
Vercel

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 climateview.global, including 12 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25