Website review, no card needed
stripo.email website review
Visit site (opens in a new tab)Reviewed 22 October 202628 issues · 80 checks
This review found 28 issues worth fixing on stripo.email, 6 of them high impact, across 80 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
84BClosest competitors among SaaS websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.5 s |
| May 9, 2026 | 2.6 s |
| May 16, 2026 | 2.6 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 3.1 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.5 s |
| Jun 27, 2026 | 3.5 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.3 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.0 s |
| Aug 15, 2026 | 3.1 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.2 s |
| Sep 12, 2026 | 2.9 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 126 ms |
| May 9, 2026 | 123 ms |
| May 16, 2026 | 122 ms |
| May 23, 2026 | 124 ms |
| May 30, 2026 | 122 ms |
| Jun 6, 2026 | 115 ms |
| Jun 13, 2026 | 114 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 132 ms |
| Jul 25, 2026 | 136 ms |
| Aug 1, 2026 | 135 ms |
| Aug 8, 2026 | 147 ms |
| Aug 15, 2026 | 146 ms |
| Aug 22, 2026 | 145 ms |
| Aug 29, 2026 | 147 ms |
| Sep 5, 2026 | 146 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 143 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 135 ms |
| Oct 17, 2026 | 135 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
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
7 third-party services on the page
7 third-party services load with your homepage (esputnik.com, stripocdn.email and cdn-cookieyes.com and others), adding 1.4 MB and 1.3 s of main-thread time.
Mobile performance score: 70
70/100Your mobile performance score is 70 (desktop: 62). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
470 ms · 390 KiBAbout 390 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.
esputnik.com adds 715 ms
715 msesputnik.com costs a phone 715 ms of main-thread work and 259 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.
stripocdn.email adds 540 ms
540 msstripocdn.email costs a phone 540 ms of main-thread work and 1.0 MB 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.
2,203 HTML elements
The page has 2,203 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
239 KiB7 images could be 239 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 174 ms. During a long task the page ignores taps.
Render-blocking requests
150 ms1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 150 ms.
Use efficient cache lifetimes
52 KiB3 files are served with short cache lifetimes, so returning visitors download them again (52 KiB).
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.
1 checks passed
Server response: 89 ms
89 msYour server sent the HTML in 89 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: 8.6 s
8.6 sThe page becomes fully interactive after 8.6 s. Good is under 3.8 s.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 3.8 s
3.8 sYour largest element takes 3.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 376 ms
376 msScripts block taps and scrolling for 376 ms in total while the page loads. 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 126 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.5 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 174 ms
174 msReal visitors wait 174 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).
Images and page weight
1 image below the first screen load straight away
1 image further down the page (86 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.5 g of CO₂ per visit
0.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.50 g of CO₂e: 60.6 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 113 requests
1.8 MBYour homepage downloads 1.8 MB in 113 requests on a phone: scripts 838 KiB (23), images 802 KiB (61) and fonts 102 KiB (2). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
ARIA dialog and alertdialog nodes should have an accessible name (2 elements)
ARIA dialog and alertdialog nodes should have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
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.
20 links without text
20 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 37 images in the HTML carry an alt attribute.
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 5 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Stripo — FREE Email Template Builder: drag-n-drop Html Email Editor”.
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.
119 internal links, 42 external
The homepage links to 119 pages on stripo.email and 42 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Stripo — free email template builder. Create professional and responsive emails fast with no HTML skills. Use it to aut…”.
One H1 headline
Your main headline reads: “Fortune 100 favorite drag-n-drop HTML email template builder”.
Canonical URL set
The canonical URL is https://stripo.email/.
Structured data in place
Structured data found: Organization, SoftwareApplication, 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://stripo.email/sitemap_index.xml.
AI search readiness
Parts of the site are closed to 2 AI crawlers
Your robots.txt lets ChatGPT search (OAI-SearchBot) and ChatGPT (ChatGPT-User) read the homepage but closes other sections to them, so answers about those pages can't cite you.
3 checks passed
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 (1,066 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://stripo.email/llms.txt (34 KiB, 40 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 14 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 14 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Cannot assign to read only property 'open' of object '#<Window>'”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
46 of 50 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 410 words of copy
The homepage carries about 410 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: “Sign up” and “Get started free”.
26 calls to action
The homepage has 26 calls to action, for example “Sign up”, “Demo” and “Learn more”.
Social proof on the page
Social proof on the homepage: 2 testimonial or review blocks, 14 customer or partner logos, a star rating and 3 trust badges.
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 (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
39 cookies set on arrival
39Opening the homepage sets 39 cookies (measured from a US location before any click).
11 other companies contacted
Loading the homepage contacts 11 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 stripo.email, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
Company
- Headquarters
- Newark
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on stripo.email, including 16 speed issues, 2 SEO issues and 1 conversion gap. 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.