Website review, no card needed
tomorrow.io website review
Visit site (opens in a new tab)Reviewed 30 October 202640 issues · 88 checks
This review found 40 issues worth fixing on tomorrow.io, 16 of them high impact, across 88 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
80BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.3 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.4 s |
| Jul 11, 2026 | 2.5 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.6 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 182 ms |
| May 16, 2026 | 195 ms |
| May 23, 2026 | 210 ms |
| May 30, 2026 | 203 ms |
| Jun 6, 2026 | 202 ms |
| Jun 13, 2026 | 198 ms |
| Jun 20, 2026 | 196 ms |
| Jun 27, 2026 | 196 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 163 ms |
| Jul 25, 2026 | 160 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 143 ms |
| Aug 22, 2026 | 144 ms |
| Aug 29, 2026 | 145 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 139 ms |
| Sep 19, 2026 | 137 ms |
| Sep 26, 2026 | 136 ms |
| Oct 3, 2026 | 142 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 148 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
3.6 s · 601 KiBAbout 601 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.
3,281 HTML elements
The page has 3,281 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and Cookiebot and others), adding 1.2 MB and 625 ms of main-thread time.
Google CDN adds 405 ms
405 msGoogle CDN costs a phone 405 ms of main-thread work and 741 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.
Render-blocking requests
350 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused CSS
150 ms · 49 KiBAbout 49 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.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
69 KiB5 files are served with short cache lifetimes, so returning visitors download them again (69 KiB).
Legacy JavaScript
25 KiBPolyfills for old browsers add 25 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.
1 checks passed
Server response: 24 ms
24 msYour server sent the HTML in 24 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.
First Contentful Paint: 7.5 s
7.5 sThe first text or image appears after 7.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “FROM SPACE DATA TO AI WEATHER DECISION”.
Time to Interactive: 11.9 s
11.9 sThe page becomes fully interactive after 11.9 s. Good is under 3.8 s.
Speed Index: 7.5 s
7.5 sVisually, the page fills in at 7.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.1 s
2.1 sReal visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.7 s
1.7 sReal visitors wait 1.7 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 214 ms
214 msScripts block taps and scrolling for 214 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 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.
Tap response (INP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 182 ms to 148 ms 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
Page weight: 7.4 MB in 92 requests
7.4 MBYour homepage downloads 7.4 MB in 92 requests on a phone: media 5.3 MB (3), scripts 1.3 MB (43) and other files 352 KiB (3). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.08 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.08 g of CO₂e: 250.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Invalid ARIA attributes
3 elements use ARIA attributes their role does not allow, which confuses screen readers.
ARIA attributes must conform to valid names (1 element)
ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (8 elements)
Scrollable region must have keyboard access: 8 elements on the page fail this check, rated serious by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
39 links without text
39 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h3 → h5, h3 → h5 and h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (10 elements).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
115 internal links, 40 external
The homepage links to 115 pages on tomorrow.io and 40 external pages.
8 checks passed
Meta description: 78 characters
Your meta description is 78 characters: “Predict, automate, and solve your biggest weather challenges with Tomorrow.io.”.
One H1 headline
Your main headline reads: “From Space Data to AI Weather Decision”.
Title: 54 characters
Your title is a healthy 54 characters: “The World’s Weather Intelligence & Resilience Platform”.
Canonical URL set
The canonical URL is https://www.tomorrow.io/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://www.tomorrow.io/sitemap.xml.
AI search readiness
3 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.
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://www.tomorrow.io/llms.txt (12 KiB, 64 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.tomorrow.io/software and https://www.tomorrow.io/weather-intelligence-platform all use the title “Tomorrow.io - The World's Weather Resilience Platform”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://www.tomorrow.io/satellite-data, https://www.tomorrow.io/consumer-app, https://www.tomorrow.io/solutions/pharmaceuticals and https://www.tomorrow.io/government-and-defense/civil-federal have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.tomorrow.io/software and https://www.tomorrow.io/weather-intelligence-platform use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.tomorrow.io/software, whose canonical is https://www.tomorrow.io/weather-intelligence-platform. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 76 found) and read each the way a search engine does.
4 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
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 13 pages that loaded have a <title>.
Best practices
7 small tap targets
7 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address 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.
Only about 134 words
The homepage has only about 134 words of visible text; thin pages give Google and first-time buyers little to go on.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Demo” and “Talk To Sales”.
31 calls to action
The homepage has 31 calls to action, for example “Learn More on Weather API”, “Get Demo” and “Talk to Sales”.
1 short form
A short form (7 fields at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 54 testimonial or review blocks, 107 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, HubSpot and Cloudflare Web Analytics.
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.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
8 other companies contacted
Loading the homepage contacts 8 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 tomorrow.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- AWS
Hiring
- Hiring
- 17 open roles
- Teams
- Space & Sensors (5), SaaS Applications (3), Open Interest Form (2), Weather (2)
- Job board
- greenhouse
- Careers page
- www.tomorrow.io/careers (opens in a new tab)
Company
- Employees
- 94
- Founded
- 2015
- Headquarters
- Boston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on tomorrow.io, including 16 speed issues, 1 SEO issue and 4 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.