Website review, no card needed
freedom.to website review
Visit site (opens in a new tab)Reviewed 19 November 202633 issues · 77 checks
This review found 33 issues worth fixing on freedom.to, 12 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| 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.3 s |
| Jul 11, 2026 | 2.3 s |
| Jul 18, 2026 | 2.3 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.1 s |
| Aug 8, 2026 | 2.1 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.4 s |
| Oct 24, 2026 | 2.4 s |
| Oct 31, 2026 | 2.4 s |
| Nov 7, 2026 | 2.6 s |
| Nov 14, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 201 ms |
| Jun 6, 2026 | 211 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 215 ms |
| Jun 27, 2026 | 215 ms |
| Jul 4, 2026 | 219 ms |
| Jul 11, 2026 | 221 ms |
| Jul 18, 2026 | 221 ms |
| Jul 25, 2026 | 215 ms |
| Aug 1, 2026 | 207 ms |
| Aug 8, 2026 | 207 ms |
| Aug 15, 2026 | 213 ms |
| Aug 22, 2026 | 220 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 228 ms |
| Sep 12, 2026 | 219 ms |
| Sep 19, 2026 | 216 ms |
| Sep 26, 2026 | 213 ms |
| Oct 3, 2026 | 212 ms |
| Oct 10, 2026 | 214 ms |
| Oct 17, 2026 | 216 ms |
| Oct 24, 2026 | 219 ms |
| Oct 31, 2026 | 221 ms |
| Nov 7, 2026 | 223 ms |
| Nov 14, 2026 | 222 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
Use efficient cache lifetimes
1.1 s · 35.5 MB23 files are served with short cache lifetimes, so returning visitors download them again (35.5 MB).
Reduce unused JavaScript
1.8 s · 348 KiBAbout 348 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Render-blocking requests
1.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and website-files.com and others), adding 36.6 MB and 832 ms of main-thread time.
website-files.com adds 120 ms
120 mswebsite-files.com costs a phone 120 ms of main-thread work and 35.7 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.
Google Tag Manager adds 396 ms
396 msGoogle Tag Manager costs a phone 396 ms of main-thread work and 532 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.
Reduce unused CSS
300 ms · 43 KiBAbout 43 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 965 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 189 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
59 KiB2 images could be 59 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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: 5 ms
5 msYour server sent the HTML in 5 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.
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 image.
Cumulative Layout Shift: 0.545
0.545The layout shifts by 0.545 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Time to Interactive: 12.3 s
12.3 sThe page becomes fully interactive after 12.3 s. Good is under 3.8 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 INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
46 images without width and height
46 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 439 ms
439 msScripts block taps and scrolling for 439 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 201 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 36.7 MB in 93 requests
36.7 MBYour homepage downloads 36.7 MB in 93 requests on a phone: media 35.0 MB (8), scripts 1,020 KiB (23) and images 517 KiB (34). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
6a636518611992a5edea018d_8d89a075bb952d7263cdab4fe23dbe70_ba is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
About 10.4 g of CO₂ per visit
10.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 10.39 g of CO₂e: 1247.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (46 elements)
All page content should be contained by landmarks: 46 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 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
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
47 internal links, 39 external
The homepage links to 47 pages on freedom.to and 39 external pages.
8 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “Freedom is the app and website blocker that syncs across Mac, Windows, iOS, Android, and Chrome. Schedule focus session…”.
One H1 headline
Your main headline reads: “Block distractions, unblock your life”.
Title: 41 characters
Your title is a healthy 41 characters: “Freedom | App, Website & Internet Blocker”.
Canonical URL set
The canonical URL is https://freedom.to/.
Structured data in place
Structured data found: FAQPage, 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://freedom.to/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, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,489 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://freedom.to/llms.txt (6 KiB, 31 links), a plain-text guide to the site for AI tools.
Other pages
6 pages without a meta description
https://freedom.to/resources, https://freedom.to/testimonials, https://freedom.to/press, https://freedom.to/partners, https://freedom.to/affiliate and https://freedom.to/contact have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://freedom.to/why and https://freedom.to/resources have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
5 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.
Titles are unique
Every page we checked has its own title.
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
2 small tap targets
2 of 8 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were 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
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 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 1,565 words of copy
The homepage carries about 1,565 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Download” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 114 testimonial or review blocks, 8 customer or partner logos, a star rating and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 1 of them by other companies (measured from a US location before any click).
19 other companies contacted
Loading the homepage contacts 19 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 freedom.to, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Webflow
- Analytics
- Google Tag Manager
- Hosting
- Cloudflare
Company
- Headquarters
- Durham
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on freedom.to, including 20 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.