Website review, no card needed
probackup.io website review
Visit site (opens in a new tab)Reviewed 10 November 202614 issues · 76 checks
This review found 14 issues worth fixing on probackup.io, 2 of them high impact, across 76 checks. The most urgent: fails Core Web Vitals for real visitors. 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
91AClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.9 s |
| May 30, 2026 | 4.4 s |
| Jun 6, 2026 | 4.9 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.3 s |
| Jul 4, 2026 | 5.5 s |
| Jul 11, 2026 | 5.9 s |
| Jul 18, 2026 | 5.8 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.4 s |
| Aug 8, 2026 | 5.7 s |
| Aug 15, 2026 | 5.7 s |
| Aug 22, 2026 | 6.1 s |
| Aug 29, 2026 | 5.9 s |
| Sep 5, 2026 | 5.8 s |
| Sep 12, 2026 | 5.7 s |
| Sep 19, 2026 | 4.3 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.1 s |
| Oct 24, 2026 | 3.0 s |
| Oct 31, 2026 | 2.9 s |
| Nov 7, 2026 | 2.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 246 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 190 ms |
| Jun 20, 2026 | 190 ms |
| Jun 27, 2026 | 240 ms |
| Jul 4, 2026 | 276 ms |
| Jul 11, 2026 | 279 ms |
| Jul 18, 2026 | 251 ms |
| Jul 25, 2026 | 246 ms |
| Aug 1, 2026 | 225 ms |
| Aug 8, 2026 | 228 ms |
| Aug 15, 2026 | 251 ms |
| Aug 22, 2026 | 251 ms |
| Aug 29, 2026 | 248 ms |
| Sep 5, 2026 | 244 ms |
| Sep 12, 2026 | 256 ms |
| Sep 19, 2026 | 255 ms |
| Sep 26, 2026 | 204 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 167 ms |
| Oct 17, 2026 | 154 ms |
| Oct 24, 2026 | 141 ms |
| Oct 31, 2026 | 128 ms |
| Nov 7, 2026 | 127 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.7 s
1.3 s
2.0 s
2.6 s
3.3 s
4.0 s
4.6 s
5.3 s
Speed
Use efficient cache lifetimes
303 KiB11 files are served with short cache lifetimes, so returning visitors download them again (303 KiB).
2,564 HTML elements
The page has 2,564 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
256 KiBAbout 256 KiB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (Facebook, Cookiebot and capterra.com and others), adding 414 KiB and 371 ms of main-thread time.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 162 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Legacy JavaScript
24 KiBPolyfills for old browsers add 24 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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92. That is in Google's “good” band (90 and up).
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 916 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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.
Time to Interactive: 9.6 s
9.6 sThe page becomes fully interactive after 9.6 s. Good is under 3.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 299 ms
299 msScripts block taps and scrolling for 299 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
7 checks passed
Real-user INP: 154 ms
154 msReal visitors wait 154 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Tap response (INP) got 41% faster for real visitors
-41%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 246 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 4.9 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest Contentful Paint: 1.9 s
1.9 sYour largest element renders in 1.9 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “SaaS vendors back up their servers. ProBackup protects your…”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Speed Index: 1.9 s
1.9 sVisually, the page fills in at 1.9 s (Speed Index), inside the 3.4 s “good” threshold.
Images and page weight
About 0.3 g of CO₂ per visit
0.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.32 g of CO₂e: 38.7 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.1 MB in 74 requests
1.1 MBYour homepage downloads 1.1 MB in 74 requests on a phone: scripts 938 KiB (19), images 86 KiB (26) and fonts 64 KiB (2). 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
31 links without text
31 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 82 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 0 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
144 internal links, 38 external
The homepage links to 144 pages on probackup.io and 38 external pages.
8 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Daily automated backups and one-click restore for Asana, monday.com, ClickUp, HubSpot, Airtable and 20+ SaaS apps. SOC …”.
One H1 headline
Your main headline reads: “SaaS vendors back up their servers. ProBackup protects your work.”.
Title: 65 characters
Your title is a healthy 65 characters: “SaaS Backup for Asana, monday.com, ClickUp & 20+ Apps | ProBackup”.
Canonical URL set
The canonical URL is https://www.probackup.io/.
Structured data in place
Structured data found: FAQPage, Organization, SoftwareApplication 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.probackup.io/sitemap-index.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (2,800 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes /llms.txt (18 KiB, 65 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 57 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
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Loading the script 'https://static.cloudflareinsights.com/beacon.min.js/vce701823e78c4301a35b7e07294d87301792088814092'…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
38 of 42 tappable elements near the top are at least 24 px.
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 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.
About 1,133 words of copy
The homepage carries about 1,133 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Start free trial” and “Start free trial →”.
15 calls to action
The homepage has 15 calls to action, for example “Start free trial”, “Pricing” and “Start free trial →”.
Social proof on the page
Social proof on the homepage: 5 testimonial or review blocks, 5 customer or partner logos, a star rating, 4 trust badges and “Over 3,000 companies”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Analytics (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 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 probackup.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Astro
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 14 issues on probackup.io, including 10 speed 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.