Loading Report View…
0/ 100
freshbus.com Website Audit Report
freshbus.com scored 67 out of 100 in this SavageAudit website audit covering Performance, SEO, Design, Copy, User Experience, and Conversion. The report uses captured website evidence to explain what is working, what is limiting the experience, and which improvements deserve attention first.
“A booking site that looks eager, then trips over its own feet.”
Fresh Bus shows up dressed for a premium ride, then leaves the booking aisle looking like it got lost between the timetable and the promo banner. The site wants to sell confidence, but it keeps crowding the aisle with enough distractions to make a traveler ask for the next departure.
https://www.freshbus.com/
TECHNICAL SUMMARY
The page has solid indexability basics, but the experience is weighed down by heavy client-side work: main-thread work is 35.1 s, bootup is 14.3 s, and Speed Index drags to 13.1 s even though first contentful paint lands at 1.4 s. Total byte weight is 4,962 KiB, cache savings are estimated at 2,177 KiB, and image delivery alone could save 573 KiB, so the fix-first move is to cut script and asset bloat before it keeps costing ticket intent and trust at the booking step.
Where It Burns
6 categoriesWebsite Audit Findings for freshbus.com
SavageAudit identified 36 visible findings and recommendations across 6 audit categories. Each section below combines the category score with observed evidence and prioritized fixes.
5201 PERFORMANCEMain-thread work 35.1 s9102 SEOSEO score 91/1007403 DESIGNImages 1188904 COPYWord count 8722105 UXBroken assets 97606 CONVERSIONCTA count 17
01
PERFORMANCE AUDIT
52
Main-thread work35.1 sBootup time14.3 sSpeed Index13.1 sTotal byte weight4,962 KiB
- 🔥First contentful paint lands in 1.4 s, then the page spends 13.1 s turning that into something usable, like an airport delay board with a sense of humor problem.
💀
A lightweight booking intent dragged under by a full cargo load of scripts and assets.
- →Defer non-critical JavaScript and reduce render-blocking resources.TBT: UnknownImpact: highEffort: medium
Why this matters
Main-thread work is 35.1 s and bootup is 14.3 s, so the browser is spending too long executing before users can book.
- →Enable CDN caching and serve static assets with long cache TTLs.FCP: 1.4 sImpact: mediumEffort: low
Why this matters
The page still carries 4,962 KiB total weight and 2,177 KiB of estimated cache savings, so cached assets would stop the same baggage from boarding every visit.
- →Compress hero images and switch to WebP/AVIF format.LCP: UnknownImpact: highEffort: medium
Why this matters
Image delivery alone could save 573 KiB, which strongly suggests the visual payload is heavier than a rush-hour suitcase rack.
02
SEO AUDIT
91
SEO score91/100Title length64 charactersSchema JSON-LD0Heading skiph1 -> h3
- 🔥The title does its job at 64 characters, but it’s still wearing a long coat into a crowded search results page.
💀
Good crawlability, but the structured data is missing and the headings are freelancing.
- →Shorten title tag to under 60 characters.Title Length: 64 charactersImpact: mediumEffort: low
Why this matters
The title is 64 characters, which is long enough to get clipped and blur the booking promise in search results.
- →Add JSON-LD structured data that matches the page type, such as WebSite, Organization, Product, or Article.Schema: NoneImpact: mediumEffort: medium
Why this matters
Schema JSON-LD is absent, so search engines lose context that could help Fresh Bus own richer travel-result visibility.
- →Add Organization or WebSite schema with sameAs links to your official LinkedIn, X, YouTube, GitHub, Crunchbase, or other canonical brand profiles.Entity Graph: MissingImpact: mediumEffort: medium
Why this matters
The entity graph is missing, so the brand’s signals are scattered instead of tied together for discoverability and trust.
03
DESIGN AUDIT
74
Images118Missing alt text6Font families6Heading count80
- 🔥There are 118 images, but 6 of them forgot alt text, so the page is visually busy and descriptively underemployed.
💀
Clean enough to function, but the visual system keeps changing buses mid-route.
- →Reduce font families from 6 to 2-3 for visual consistency.Font Families: 6Impact: mediumEffort: low
Why this matters
Six font families is too many for a booking flow that should feel steady and legible, not like the typography is switching drivers.
- →Fix missing alt text to pass accessibility audits.Missing Alt: 6Impact: mediumEffort: medium
Why this matters
Six missing alt attributes on 118 images means meaningful visuals are arriving without labels, which hurts accessibility and polish.
- →Add supporting imagery so the layout feels intentional, not empty.Images: 118Impact: mediumEffort: medium
Why this matters
With 118 images already on the page, the visual density needs to feel purposeful instead of crowded and partially cut off.
04
COPY AUDIT
89
Word count872Sentence count47CTA count17Meta description length143 characters
- 🔥The meta description is 143 characters and repeats 'Book bus ticket booking service easy and securely,' which is doing the same job twice and nailing it neither time.
💀
The words mostly work, but they’re crowded, repetitive, and slightly out of sync with the promise.
- →Tighten the headline to state your value in one sentence.H1 Count: 1Impact: mediumEffort: low
Why this matters
There is one H1, so that headline needs to do more work instead of splitting the booking promise across title and hero.
- →Break long paragraphs into skimmable bullets and shorter sentences.Avg Words/Sentence: 19Impact: lowEffort: medium
Why this matters
The page has 47 sentences and 872 words, so tighter sentence structure would make route, pricing, and refund info easier to scan.
- →Add a clear CTA - make the primary one stand out.CTA Count: 17Impact: mediumEffort: low
Why this matters
Seventeen CTAs is a lot of boarding announcements for one homepage, and the primary booking action needs to stop competing with itself.
05
UX AUDITUSER EXPERIENCE AUDIT
21
Broken assets9Nav/footerNo nav / No footerButtons36Inputs3
- 🔥There are 9 broken assets, including 8 fetch failures and one busted freshPromise request, so parts of the page are literally not showing up for duty.
💀
A booking experience with missing pieces, missing wayfinding, and more buttons than guidance.
- →Repair failed asset URLs and deployment paths so scripts, images, and stylesheets load cleanly.Broken Assets: 9Impact: highEffort: medium
Why this matters
Nine broken assets mean users are hitting dead ends before they even reach the booking flow, which is brutal for trust.
- →Ensure consistent navigation and footer links across all pages.Nav/Footer: No nav / No footerImpact: mediumEffort: medium
Why this matters
Without nav or footer, travelers lose the basic wayfinding they need to check routes, support, and coverage.
- →Reduce form fields (currently 3) to only the essentials.Form Fields: 3Impact: lowEffort: medium
Why this matters
Even though the form surface is small, every field matters in a ticket-booking flow where users want the fastest possible path to seats.
06
CONVERSION AUDIT
76
CTA count17Social proof1Forms0Required inputs0
- 🔥There are 17 CTAs on this page, so the booking pitch is less 'pick your ride' and more 'choose your own confusion.'
💀
The page can point to booking, but it keeps making users work for the final click.
- →Add a primary CTA above the fold that matches your core offer.CTA Count: 17Impact: mediumEffort: low
Why this matters
Seventeen CTAs without one dominant booking action turns the homepage into a bus stand full of signs and no obvious ticket counter.
- →Include social proof or trust signals (testimonials, logos, stats) near the CTA.Social Proof: 1Impact: mediumEffort: low
Why this matters
Only one social-proof signal is available, so the booking CTA needs closer proof that the ride is worth committing to.
- →Offer a low-friction contact option - form, chat, or visible email.Contact Path: PresentImpact: lowEffort: medium
Why this matters
The page relies on links rather than a direct capture path, so adding a low-friction contact option would help rescue abandoned booking intent.
Audit overview
freshbus.com Audit Summary
The page has solid indexability basics, but the experience is weighed down by heavy client-side work: main-thread work is 35.1 s, bootup is 14.3 s, and Speed Index drags to 13.1 s even though first contentful paint lands at 1.4 s. Total byte weight is 4,962 KiB, cache savings are estimated at 2,177 KiB, and image delivery alone could save 573 KiB, so the fix-first move is to cut script and asset bloat before it keeps costing ticket intent and trust at the booking step.
Based on the category scores in this report, SEO is the strongest area while User Experience has the most room for improvement.
How SavageAudit Evaluated freshbus.com
SavageAudit evaluated the public website at https://www.freshbus.com/ across performance, technical SEO, design, copy, user experience, and conversion signals. Scores and recommendations reflect the website evidence available when this audit was generated on July 11, 2026.
Similar Website Audit Reports
Compare this result with other public SavageAudit reports that received a similar overall website score.