Website review, no card needed
exalate.com website review
Visit site (opens in a new tab)Reviewed 24 October 202627 issues · 81 checks
This review found 27 issues worth fixing on exalate.com, 11 of them high impact, across 81 checks. The most urgent: render-blocking requests. 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
76CClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.8 s |
| May 9, 2026 | 4.9 s |
| May 16, 2026 | 4.8 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.0 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.4 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 5.1 s |
| Oct 3, 2026 | 5.1 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 264 ms |
| May 9, 2026 | 221 ms |
| May 16, 2026 | 240 ms |
| May 23, 2026 | 258 ms |
| May 30, 2026 | 263 ms |
| Jun 6, 2026 | 283 ms |
| Jun 13, 2026 | 252 ms |
| Jun 20, 2026 | 236 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 233 ms |
| Jul 11, 2026 | 249 ms |
| Jul 18, 2026 | 255 ms |
| Jul 25, 2026 | 232 ms |
| Aug 1, 2026 | 219 ms |
| Aug 8, 2026 | 213 ms |
| Aug 15, 2026 | 193 ms |
| Aug 22, 2026 | 206 ms |
| Aug 29, 2026 | 224 ms |
| Sep 5, 2026 | 237 ms |
| Sep 12, 2026 | 232 ms |
| Sep 19, 2026 | 255 ms |
| Sep 26, 2026 | 263 ms |
| Oct 3, 2026 | 256 ms |
| Oct 10, 2026 | 265 ms |
| Oct 17, 2026 | 260 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
Render-blocking requests
4.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.4 s.
Use efficient cache lifetimes
1.8 s · 305 KiB11 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
Reduce unused CSS
900 ms · 174 KiBAbout 174 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.
Reduce unused JavaScript
900 ms · 132 KiBAbout 132 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56 (desktop: 89). Pages that score under 90 lose visitors before the first paint.
2,209 HTML elements
The page has 2,209 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
7 third-party services on the page
7 third-party services load with your homepage (Facebook, Google Tag Manager and Hubspot and others), adding 602 KiB and 392 ms of main-thread time.
Legacy JavaScript
200 ms · 26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 89 but mobile only 56. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 494 ms of it running JavaScript. That is comfortably low.
Server response: 86 ms
86 msYour server sent the HTML in 86 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.
Real-user LCP: 4.8 s
4.8 sReal visitors wait 4.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.7 s
4.7 sReal visitors see the first content after 4.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 12.2 s
12.2 sYour largest element takes 12.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Real-time, two-way sync shaped by how you collaborate. Exal…”.
First Contentful Paint: 6.6 s
6.6 sThe first text or image appears after 6.6 s on a phone. Good is under 1.8 s.
Time to Interactive: 12.4 s
12.4 sThe page becomes fully interactive after 12.4 s. Good is under 3.8 s.
Speed Index: 6.6 s
6.6 sVisually, the page fills in at 6.6 s (Speed Index). Good is under 3.4 s.
Real-user INP: 274 ms
274 msReal visitors wait 274 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 264 ms to 260 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 179 ms
179 msScripts block the page for only 179 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.4 g of CO₂ per visit
0.43 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.43 g of CO₂e: 51.1 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: 1.5 MB in 50 requests
1.5 MBYour homepage downloads 1.5 MB in 50 requests on a phone: fonts 621 KiB (13), scripts 519 KiB (11) and stylesheets 194 KiB (3). 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Main landmark should not be contained in another landmark (1 element)
Main landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
10 links without text
10 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4, h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 84 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
167 internal links, 34 external
The homepage links to 167 pages on exalate.com and 34 external pages.
8 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “The only real-time bidirectional integration solution built specifically for complex cross-team collaboration cases and…”.
One H1 headline
Your main headline reads: “Where Integrations Don’t Hit Limits”.
Title: 36 characters
Your title is a healthy 36 characters: “Exalate - Integration Without Limits”.
Canonical URL set
The canonical URL is https://exalate.com/.
Structured data in place
Structured data found: Organization, Person 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.
XML sitemap found
Your XML sitemap is reachable at https://exalate.com/sitemap.xml.
AI search readiness
4 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, sameAs (social profiles) and description; logo and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (880 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://exalate.com/llms.txt (79 KiB, 202 links), a plain-text guide to the site for AI tools.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 73 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 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “wp is not defined”.
2 checks passed
Tap targets are thumb-sized
10 of 10 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. 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 613 words of copy
The homepage carries about 613 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: “START FOR FREE” and “BOOK A DEMO”.
17 calls to action
The homepage has 17 calls to action, for example “Pricing”, “Contact Us” and “START FOR FREE”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Tag Manager, Hotjar, HubSpot, LinkedIn Insight and Meta Pixel and 4 mores (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
39 other companies contacted
Loading the homepage contacts 39 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) 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 exalate.com, 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 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 27 issues on exalate.com, including 15 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.