Website review, no card needed
fretron.com website review
Visit site (opens in a new tab)Reviewed 11 November 202616 issues · 73 checks
This review found 16 issues worth fixing on fretron.com, 3 of them high impact, across 73 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
97AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.6 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 155 ms |
| May 30, 2026 | 147 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 133 ms |
| Jun 20, 2026 | 136 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 141 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 152 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 164 ms |
| Aug 15, 2026 | 164 ms |
| Aug 22, 2026 | 159 ms |
| Aug 29, 2026 | 163 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 182 ms |
| Oct 3, 2026 | 204 ms |
| Oct 10, 2026 | 201 ms |
| Oct 17, 2026 | 201 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.6 s
1.2 s
1.7 s
2.3 s
2.9 s
3.5 s
4.1 s
4.6 s
Speed
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 1.1 MB and 703 ms of main-thread time.
Render-blocking requests
650 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.
Google Tag Manager adds 376 ms
376 msGoogle Tag Manager costs a phone 376 ms of main-thread work and 654 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.
Use efficient cache lifetimes
394 KiB13 files are served with short cache lifetimes, so returning visitors download them again (394 KiB).
Reduce unused JavaScript
374 KiBAbout 374 KiB of JavaScript is downloaded but never used on this page.
Facebook adds 191 ms
191 msFacebook costs a phone 191 ms of main-thread work and 311 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.
1,637 HTML elements
The page has 1,637 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 213 ms. During a long task the page ignores taps.
Legacy JavaScript
26 KiBPolyfills for old browsers add 26 KiB JavaScript that modern phones do not need.
Improve image delivery
13 KiB3 images could be 13 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.
3 checks passed
Mobile performance score: 94
94/100Your mobile performance score is 94. That is in Google's “good” band (90 and up).
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 887 ms of it running JavaScript. That is comfortably low.
Server response: 22 ms
22 msYour server sent the HTML in 22 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: 10.2 s
10.2 sThe page becomes fully interactive after 10.2 s. Good is under 3.8 s.
Tap response (INP) got 33% slower for real visitors
+33%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 155 ms to 201 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 872 ms
872 msReal visitors wait 872 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
24 images without width and height
24 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 218 ms
218 msScripts block taps and scrolling for 218 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.7 s
1.7 sReal visitors see the first content after 1.7 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Largest Contentful Paint: 1.2 s
1.2 sYour largest element renders in 1.2 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “One record per order — captured, tracked, and tied out end …”.
Images and page weight
About 0.4 g of CO₂ per visit
0.37 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.37 g of CO₂e: 44.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.3 MB in 64 requests
1.3 MBYour homepage downloads 1.3 MB in 64 requests on a phone: scripts 1.1 MB (18), fonts 57 KiB (2) and HTML 46 KiB (1). 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
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
163 internal links, 7 external
The homepage links to 163 pages on fretron.com and 7 external pages.
8 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “Your margin leaks between your OMS, WMS, and courier panel. Fretron runs orders, warehouse, and delivery on one record.…”.
One H1 headline
Your main headline reads: “One record per order — captured, tracked, and tied out end to end.”.
Title: 64 characters
Your title is a healthy 64 characters: “Fretron — Fulfillment Platform for Consumer Brands | OMS WMS TMS”.
Canonical URL set
The canonical URL is https://www.fretron.com/.
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.fretron.com/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: 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 (2,715 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fretron.com/llms.txt (1 KiB, 10 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
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 6 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 1,992 words of copy
The homepage carries about 1,992 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book a demo on your order flow”.
14 calls to action
The homepage has 14 calls to action, for example “Omnichannel Order Management”, “Order Management System (OMS)” and “Book a Demo”.
3 short forms
3 short forms (3 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, 23 customer or partner logos and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
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
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 2 mores (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.
16 cookies set on arrival
16Opening the homepage sets 16 cookies, 6 of them by other companies (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.
24 other companies contacted
Loading the homepage contacts 24 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 fretron.com, 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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Vercel
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 fretron.com, including 14 speed issues. 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.