Website review, no card needed
vodafone.com.fj website review
Visit site (opens in a new tab)Reviewed 28 October 202647 issues · 91 checks
This review found 47 issues worth fixing on vodafone.com.fj, 21 of them high impact, across 91 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 4.1 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 3.7 s |
| Aug 8, 2026 | 8.9 s |
| Aug 15, 2026 | 8.7 s |
| Aug 22, 2026 | 8.5 s |
| Aug 29, 2026 | 7.7 s |
| Sep 5, 2026 | 7.5 s |
| Oct 10, 2026 | 5.7 s |
| Oct 24, 2026 | 5.7 s |
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
3.8 s
7.5 s
11.3 s
15.0 s
18.8 s
22.5 s
26.3 s
30.0 s
Speed
Improve image delivery
24.1 s · 6.5 MB19 images could be 6.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.1 s faster on a phone.
Render-blocking requests
7.8 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.8 s.
Reduce unused JavaScript
4.3 s · 864 KiBAbout 864 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.7 s · 305 KiB12 files are served with short cache lifetimes, so returning visitors download them again (305 KiB).
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Document request latency
1.3 s · 143 KiBThe HTML itself could arrive about 1.3 s sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce initial server response time
1.2 sReduce initial server response time. Google estimates savings of 1.2 s on a phone.
Mobile performance score: 19
19/100Your mobile performance score is 19 (desktop: 23). 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, ZenDesk and Facebook and others), adding 1.3 MB and 969 ms of main-thread time.
Reduce unused CSS
600 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Google Tag Manager adds 408 ms
408 msGoogle Tag Manager costs a phone 408 ms of main-thread work and 522 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 414 ms. During a long task the page ignores taps.
Main-thread work: 3.6 s
A phone's processor spends 3.6 s on main-thread work while loading, 2.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 12 KiBPolyfills for old browsers add 12 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
ZenDesk adds 214 ms
214 msZenDesk costs a phone 214 ms of main-thread work and 415 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,378 HTML elements
The page has 2,378 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.3 s
1.3 sYour server takes 1.3 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
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.
Real-user LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.4 s
5.4 sReal visitors see the first content after 5.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 93.3 s
93.3 sYour largest element takes 93.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Speed Index: 56.0 s
56.0 sVisually, the page fills in at 56.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 94.1 s
94.1 sThe page becomes fully interactive after 94.1 s. Good is under 3.8 s.
First Contentful Paint: 7.4 s
7.4 sThe first text or image appears after 7.4 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.573
0.573The layout shifts by 0.573 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.1 s to 5.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 566 ms
566 msScripts block taps and scrolling for 566 ms in total while the page loads. Good is under 200 ms.
29 images without width and height
29 images have no width and height attributes, so the layout jumps as each one loads.
2 checks passed
Real-user INP: 138 ms
138 msReal visitors wait 138 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.06
0.06For real visitors the layout shifts by 0.06 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 18.5 MB in 164 requests
18.5 MBYour homepage downloads 18.5 MB in 164 requests on a phone: images 15.9 MB (63), scripts 1.9 MB (49) and fonts 263 KiB (6). Under 2 MB keeps phones on slow connections fast.
About 5.2 g of CO₂ per visit
5.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.24 g of CO₂e: 628.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
4 buttons without a name
4 buttons have no accessible name, so screen readers announce just “button”.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h1 → h4, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 59 images in the HTML carry an alt attribute.
SEO
Title is short (24 characters)
Your title is only 24 characters: “Vodafone Fiji - Personal”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Products you will Love” and “Learn More”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: sameAs is not an absolute URL ("www.facebook.com/vodafoneFiji")”.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
472 internal links, 26 external
The homepage links to 472 pages on vodafone.com.fj and 26 external pages.
4 checks passed
Meta description: 113 characters
Your meta description is 113 characters: “Mobile telecommunications company. Includes outlet maps, on-line service, network information, and pricing plans.”.
Canonical URL set
The canonical URL is https://vodafone.com.fj/.
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.vodafone.com.fj/sitemap/sitemap-index.xml.
AI search readiness
No llms.txt
There is no https://vodafone.com.fj/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: 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 (3,082 words), so crawlers that don't run JavaScript still read it.
Other pages
8 pages share a meta description
https://vodafone.com.fj/help, https://vodafone.com.fj/about, https://vodafone.com.fj/my-vodafone/web-top-up, https://vodafone.com.fj/personal/price-plans, https://vodafone.com.fj/personal/price-plans/mobile-internet and https://vodafone.com.fj/personal/price-plans/mobile-internet/555-bundles and 2 others use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://vodafone.com.fj/about, whose canonical is https://vodafone.com.fj/about/about-us/vodafone-fiji. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page slow to respond
https://vodafone.com.fj/about took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 196 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
17 of 18 tappable elements near the top are at least 24 px.
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.
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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 287 words of copy
The homepage carries about 287 words of visible text.
4 checks passed
44 calls to action
The homepage has 44 calls to action, for example “Call Me Back & Recharge Me Services”, “Buy Data and Win Promotions” and “Buy Data and WIN a Cinematic Experience”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Opening hours shown
Your opening hours are on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight and 1 more (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.
12 cookies set on arrival
12Opening the homepage sets 12 cookies (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.
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.
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 vodafone.com.fj, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Sitefinity 11.2.6900.0 OME
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Vodafone Fiji Limited
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on vodafone.com.fj, including 29 speed issues, 4 SEO issues and 5 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.