Website review, no card needed
vodafone.om website review
Visit site (opens in a new tab)Reviewed 17 November 202650 issues · 91 checks
This review found 50 issues worth fixing on vodafone.om, 21 of them high impact, across 91 checks. The most urgent: render-blocking requests. 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
67DClosest 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.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 2.4 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.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.6 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.4 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
| Nov 7, 2026 | 2.2 s |
| Nov 14, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 216 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 221 ms |
| Jun 20, 2026 | 224 ms |
| Jun 27, 2026 | 224 ms |
| Jul 4, 2026 | 277 ms |
| Jul 11, 2026 | 276 ms |
| Jul 18, 2026 | 273 ms |
| Jul 25, 2026 | 267 ms |
| Aug 1, 2026 | 228 ms |
| Aug 8, 2026 | 237 ms |
| Aug 15, 2026 | 242 ms |
| Aug 22, 2026 | 249 ms |
| Aug 29, 2026 | 250 ms |
| Sep 5, 2026 | 242 ms |
| Sep 12, 2026 | 239 ms |
| Sep 19, 2026 | 240 ms |
| Sep 26, 2026 | 239 ms |
| Oct 3, 2026 | 241 ms |
| Oct 10, 2026 | 245 ms |
| Oct 17, 2026 | 249 ms |
| Oct 24, 2026 | 257 ms |
| Oct 31, 2026 | 258 ms |
| Nov 7, 2026 | 250 ms |
| Nov 14, 2026 | 239 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
1.5 s
3.0 s
4.5 s
6.0 s
7.4 s
8.9 s
10.4 s
11.9 s
Speed
Render-blocking requests
5.5 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 5.5 s.
Reduce unused JavaScript
3.5 s · 1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 563 KiB19 files are served with short cache lifetimes, so returning visitors download them again (563 KiB).
Reduce unused CSS
1.6 s · 292 KiBAbout 292 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Font display
1.5 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.5 s).
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 3.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
600 ms · 2.7 MB6 images could be 2.7 MB 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 2.4 s. During a long task the page ignores taps.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 1.8 MB and 1.1 s of main-thread time.
Google Tag Manager adds 530 ms
530 msGoogle Tag Manager costs a phone 530 ms of main-thread work and 868 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.
Facebook adds 222 ms
222 msFacebook costs a phone 222 ms of main-thread work and 303 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,212 HTML elements
The page has 2,212 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
106 KiB106 KiB could be saved by minifying JavaScript.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
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: 203 ms
203 msYour server sent the HTML in 203 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: 19.3 s
19.3 sYour largest element takes 19.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “iPhone 18 Pro Pro further. Order now”.
Speed Index: 18.4 s
18.4 sVisually, the page fills in at 18.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 33.4 s
33.4 sThe page becomes fully interactive after 33.4 s. Good is under 3.8 s.
First Contentful Paint: 5.2 s
5.2 sThe first text or image appears after 5.2 s on a phone. Good is under 1.8 s.
Total Blocking Time: 1.5 s
1.5 sScripts block taps and scrolling for 1.5 s in total while the page loads. Good is under 200 ms.
Real-user INP: 266 ms
266 msReal visitors wait 266 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Cumulative Layout Shift: 0.137
0.137The layout shifts by 0.137 while loading, so content jumps under the reader's thumb. Good is under 0.1.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 216 ms to 239 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.10
0.10For real visitors the layout shifts by 0.10 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 580 ms
580 msReal visitors wait 580 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 7.1 MB in 133 requests
7.1 MBYour homepage downloads 7.1 MB in 133 requests on a phone: scripts 3.3 MB (46), images 3.1 MB (32) and stylesheets 326 KiB (11). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 2.3 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.5 MB3 images are downloaded at several times the size a phone draws them, for example 2113213157-VF-Atlas-2026-Website-Fornt-Page-1153X1445PX-1.jp at 1,153 px wide, shown at 288 px. Resized copies would save about 1.5 MB.
3 images in older formats
3 images (2.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 2.0 g of CO₂ per visit
2.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.01 g of CO₂e: 240.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Orphan list items
Some list items are not inside a list.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 18 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (15 characters)
Your title is only 15 characters: “Home - Vodafone”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“iPhone 18 Pro” and “Your World Plans”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://www.vodafone.om/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at vodafone.om/robots.txt, the first file search crawlers ask for.
Open Graph partly set
Open Graph is missing og:description, so shared links fall back to guesses.
68 internal links, 29 external
The homepage links to 68 pages on vodafone.om and 29 external pages.
2 checks passed
Canonical URL set
The canonical URL is https://www.vodafone.om/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://www.vodafone.om/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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (261 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
https://www.vodafone.om/plans and https://www.vodafone.om/plans/prepaid all use the title “Vodafone RED - Vodafone”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://www.vodafone.om/privacy-policy, https://www.vodafone.om/business/home, https://www.vodafone.om/ar, https://www.vodafone.om/plans, https://www.vodafone.om/plans/prepaid and https://www.vodafone.om/plans/post-pay and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.vodafone.om/plans, whose canonical is https://www.vodafone.om/plans/prepaid. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://www.vodafone.om/wafi-rewards has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.vodafone.om/ar has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
2 pages slow to respond
https://www.vodafone.om/privacy-policy and https://www.vodafone.om/plans took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_SSL_PROTOCOL_ERROR”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
2 checks passed
Tap targets are thumb-sized
39 of 48 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
Only about 170 words
The homepage has only about 170 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop” and “Subscribe Now”.
10 calls to action
The homepage has 10 calls to action, for example “Shop”, “Order now” and “Subscribe Now”.
2 short forms
2 short forms (3 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Snap Pixel 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.
30 cookies set on arrival
30Opening the homepage sets 30 cookies, 2 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.
28 other companies contacted
Loading the homepage contacts 28 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.om, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Oman Future Telecommunications Company SAOC
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on vodafone.om, including 22 speed issues, 5 SEO issues and 3 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.