Website review, no card needed
fello.com website review
Visit site (opens in a new tab)Reviewed 14 November 202629 issues · 84 checks
This review found 29 issues worth fixing on fello.com, 12 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.1 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 4.0 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.7 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 3.2 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 6, 2026 | 409 ms |
| Jun 13, 2026 | 326 ms |
| Jun 20, 2026 | 326 ms |
| Jun 27, 2026 | 327 ms |
| Jul 4, 2026 | 199 ms |
| Aug 22, 2026 | 135 ms |
| Sep 19, 2026 | 252 ms |
| Sep 26, 2026 | 257 ms |
| Oct 3, 2026 | 236 ms |
| Oct 10, 2026 | 213 ms |
| Oct 17, 2026 | 218 ms |
| Oct 24, 2026 | 221 ms |
| Oct 31, 2026 | 233 ms |
| Nov 7, 2026 | 245 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
Reduce unused JavaScript
4.3 s · 920 KiBAbout 920 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 737 KiB23 files are served with short cache lifetimes, so returning visitors download them again (737 KiB).
Mobile performance score: 37
37/100Your mobile performance score is 37. 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, hsappstatic.net and Hubspot and others), adding 2.2 MB and 1.3 s of main-thread time.
Improve image delivery
600 ms · 223 KiB7 images could be 223 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 414 ms
414 msGoogle Tag Manager costs a phone 414 ms of main-thread work and 529 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.
hsappstatic.net adds 326 ms
326 mshsappstatic.net costs a phone 326 ms of main-thread work and 818 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.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Hubspot adds 191 ms
191 msHubspot costs a phone 191 ms of main-thread work and 363 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.
2,035 HTML elements
The page has 2,035 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
250 ms · 68 KiBPolyfills for old browsers add 68 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 197 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.
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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 25 ms
25 msYour server sent the HTML in 25 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.
First Contentful Paint: 10.4 s
10.4 sThe first text or image appears after 10.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 22.4 s
22.4 sYour largest element takes 22.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 24.6 s
24.6 sThe page becomes fully interactive after 24.6 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.20
0.20For real visitors the layout shifts by 0.20 (75th percentile). Good is under 0.1.
Largest content (LCP) got 53% slower for real visitors
+53%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.1 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 506 ms
506 msScripts block taps and scrolling for 506 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.154
0.154The layout shifts by 0.154 while loading, so content jumps under the reader's thumb. Good is under 0.1.
4 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 535 ms
535 msReal visitors wait 535 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 35% faster for real visitors
-35%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 409 ms to 245 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.5 MB in 191 requests
4.5 MBYour homepage downloads 4.5 MB in 191 requests on a phone: scripts 2.9 MB (65), media 774 KiB (2) and images 614 KiB (69). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image 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 1.3 g of CO₂ per visit
1.29 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.29 g of CO₂e: 154.7 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
Links look like plain text
50 links inside paragraphs rely on colour alone to stand out.
12 tap targets too small
12 tap targets are too small or too close together to hit reliably with a finger.
2 checks passed
Every image has alt text
All 157 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 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 2 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
116 internal links, 6 external
The homepage links to 116 pages on fello.com and 6 external pages.
8 checks passed
Meta description: 106 characters
Your meta description is 106 characters: “Power your gathering with bulk event technology rentals - POS systems, iPads, kiosks, and Wi-Fi solutions.”.
One H1 headline
Your main headline reads: “The Event Tech Rental Partner You'll Fello in Love With”.
Title: 54 characters
Your title is a healthy 54 characters: “Event Tech Rentals: iPads, POS, Kiosks & Wi-Fi | Fello”.
Canonical URL set
The canonical URL is https://fello.com/.
Structured data in place
Structured data found: Organization 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://fello.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://fello.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
3 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,532 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages slow to respond
https://fello.com/partner/square, https://fello.com/ipad-rentals, https://fello.com/event-wifi, https://fello.com/laptop, https://fello.com/iphone-rentals and https://fello.com/event-printer-and-scanner-rentals and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 86 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 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=5442476&tm=gtm002&Ver=2&mid=386da7dc-0ee5-45c0-8c1f-4b45b99a7f9a&bo=1&sid=7f127290e05311f1a19add10799d8276&vid=7f128760e05311f1b82ac7e8d0babe9f&vids=1&msclkid=N&page_p.
11 small tap targets
11 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
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”.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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 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.
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 2,505 words of copy
The homepage carries about 2,505 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: “Subscribe Now” and “Get a Quote”.
8 calls to action
The homepage has 8 calls to action, for example “Contact”, “Get a Quote” and “Learn More”.
Social proof on the page
Social proof on the homepage: 3 testimonial or review blocks, 1 customer or partner logo and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and HubSpot.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.
43 cookies set on arrival
43Opening the homepage sets 43 cookies, 15 of them by other companies (measured from a US location before any click).
48 other companies contacted
Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: HubSpot cookie banner
A consent management tool (HubSpot cookie banner) 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 fello.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
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- AWS
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on fello.com, including 19 speed issues, 1 SEO issue 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.