Website review, no card needed
tempest.im website review
Visit site (opens in a new tab)Reviewed 20 October 202616 issues · 73 checks
This review found 16 issues worth fixing on tempest.im, 5 of them high impact, across 73 checks. The most urgent: frames without titles. 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
88BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Mobile performance score: 81
81/100Your mobile performance score is 81 (desktop: 61). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
460 ms · 215 KiBAbout 215 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 460 ms faster on a phone.
Google Tag Manager adds 225 ms
225 msGoogle Tag Manager costs a phone 225 ms of main-thread work and 330 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.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Google Analytics and Adobe TypeKit and others), adding 594 KiB and 267 ms of main-thread time.
Reduce unused CSS
150 ms · 45 KiBAbout 45 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 151 ms. During a long task the page ignores taps.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Use efficient cache lifetimes
32 KiB7 files are served with short cache lifetimes, so returning visitors download them again (32 KiB).
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 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.
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.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 460 ms of it running JavaScript. That is comfortably low.
Server response: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 7.0 s
7.0 sThe page becomes fully interactive after 7.0 s. Good is under 3.8 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
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.
3 checks passed
Speed Index: 2.9 s
2.9 sVisually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.
Total Blocking Time: 68 ms
68 msScripts block the page for only 68 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 28.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 851 KiB in 42 requests
851 KiBYour homepage downloads 851 KiB in 42 requests on a phone: scripts 517 KiB (18), fonts 162 KiB (8) and images 49 KiB (8). That is a lean page.
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
Frames without titles
4 frames have no title, so screen-reader users cannot tell what they contain.
[role="img"] and [role="image"] elements must have alternative text (4 elements)
[role="img"] and [role="image"] elements must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.
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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 50 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
99 internal links, 27 external
The homepage links to 99 pages on tempest.im and 27 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Tempest helps innovative Destination Organizations grow and strengthen their communities by providing Software, Web, an…”.
One H1 headline
Your main headline reads: “Tempest bolt”.
Title: 57 characters
Your title is a healthy 57 characters: “Tempest / Tempest | Destination Websites, CRM & Marketing”.
Canonical URL set
The canonical URL is https://www.tempest.im/.
Structured data in place
Structured data found: BreadcrumbList, LocalBusiness and Organization.
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.destinationsignals.com/sitemaps-1-sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.tempest.im/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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (537 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 30 found) and read each the way a search engine does.
7 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.
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
2 small tap targets
2 of 10 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
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 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.
About 393 words of copy
The homepage carries about 393 words of visible text.
5 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact Us”, “Get In Touch →” and “Learn More”.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks and 1 customer or partner logo.
Analytics in place
Analytics detected: Google Tag Manager and Cloudflare Web Analytics.
Phone number on the homepage
Your phone number is on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, 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.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
No consent tool detected
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.
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 tempest.im, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 16 issues on tempest.im, including 6 speed issues, 1 SEO issue 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.