Website review, no card needed
lanzatech.com website review
Visit site (opens in a new tab)Reviewed 2 November 202630 issues · 76 checks
This review found 30 issues worth fixing on lanzatech.com, 8 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.2 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.8 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 3.1 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.5 s |
| Oct 10, 2026 | 4.2 s |
| Oct 17, 2026 | 3.8 s |
| Oct 24, 2026 | 3.6 s |
| Oct 31, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 81 ms |
| May 23, 2026 | 83 ms |
| May 30, 2026 | 84 ms |
| Jun 6, 2026 | 83 ms |
| Jun 13, 2026 | 86 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 86 ms |
| Jul 4, 2026 | 87 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 82 ms |
| Jul 25, 2026 | 82 ms |
| Aug 1, 2026 | 81 ms |
| Aug 8, 2026 | 82 ms |
| Aug 15, 2026 | 94 ms |
| Aug 22, 2026 | 94 ms |
| Aug 29, 2026 | 94 ms |
| Sep 5, 2026 | 94 ms |
| Sep 12, 2026 | 93 ms |
| Sep 19, 2026 | 90 ms |
| Sep 26, 2026 | 92 ms |
| Oct 3, 2026 | 94 ms |
| Oct 10, 2026 | 92 ms |
| Oct 17, 2026 | 117 ms |
| Oct 24, 2026 | 117 ms |
| Oct 31, 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
Speed
Use efficient cache lifetimes
1.1 s · 634 KiB66 files are served with short cache lifetimes, so returning visitors download them again (634 KiB).
Render-blocking requests
1.1 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 72
72/100Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
300 ms · 615 KiB4 images could be 615 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Reduce unused JavaScript
450 ms · 121 KiBAbout 121 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 64 KiBAbout 64 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
3 third-party services on the page
3 third-party services load with your homepage (Cookiebot, Google Tag Manager and Google Fonts), adding 339 KiB and 142 ms of main-thread time.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 214 ms of it running JavaScript. That is comfortably low.
Server response: 8 ms
8 msYour server sent the HTML in 8 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.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use essential cookies to ensure this website functions p…”. Most of its time is element render delay (3.0 s).
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 81 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 5.3 s
5.3 sVisually, the page fills in at 5.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 5.9 s
5.9 sThe page becomes fully interactive after 5.9 s. Good is under 3.8 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.2 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 87 ms
87 msReal visitors wait 87 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (67 KiB) is 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.
About 0.5 g of CO₂ per visit
0.51 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.51 g of CO₂e: 61.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 1.8 MB in 75 requests
1.8 MBYour homepage downloads 1.8 MB in 75 requests on a phone: images 913 KiB (9), scripts 572 KiB (36) and fonts 251 KiB (4). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 10 images in the HTML carry an alt attribute.
41 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
70 internal links, 13 external
The homepage links to 70 pages on lanzatech.com and 13 external pages.
4 checks passed
Title: 41 characters
Your title is a healthy 41 characters: “LanzaTech – Recycling carbon with biology”.
Canonical URL set
The canonical URL is https://lanzatech.com/.
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://lanzatech.com/wp-sitemap.xml.
AI search readiness
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://lanzatech.com/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 (705 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages without a meta description
https://lanzatech.com/about, https://lanzatech.com/biorefining, https://lanzatech.com/porsgrunn, https://lanzatech.com/biorefining/lanzatech-project-flite, https://lanzatech.com/saf and https://lanzatech.com/lnp and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://lanzatech.com/about, https://lanzatech.com/biorefining, https://lanzatech.com/porsgrunn, https://lanzatech.com/biorefining/lanzatech-project-flite, https://lanzatech.com/saf and https://lanzatech.com/lnp and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages slow to respond
https://lanzatech.com/saf, https://lanzatech.com/privacy-policy and https://lanzatech.com/terms-of-use took over 3 s to send their HTML from our server.
12 internal pages checked
We fetched 12 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 12 pages that loaded have a <title>.
Best practices
2 small tap targets
2 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. 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 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 610 words of copy
The homepage carries about 610 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “LEARN MORE”.
7 calls to action
The homepage has 7 calls to action, for example “Contact” and “Learn more”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 lanzatech.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2022.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Sucuri
Company
- Employees
- 170
- Founded
- 2005
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 30 issues on lanzatech.com, including 15 speed issues, 4 SEO 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.