Website review, no card needed

pepsioman.com logo

pepsioman.com website review

Visit site (opens in a new tab)Reviewed 19 November 202644 issues · 85 checks

This review found 44 issues worth fixing on pepsioman.com, 17 of them high impact, across 85 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
4.0 s2.7 sAug 15Sep 193.7 s
Show as table
DateReal-visitor load time (LCP)
Aug 15, 20262.8 s
Aug 22, 20263.0 s
Aug 29, 20263.3 s
Sep 5, 20263.5 s
Sep 12, 20263.8 s
Sep 19, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
110 ms103 msAug 22Sep 19109 ms
Show as table
DateReal-visitor tap response (INP)
Aug 22, 2026104 ms
Aug 29, 2026104 ms
Sep 5, 2026107 ms
Sep 12, 2026105 ms
Sep 19, 2026109 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

Full-page screenshot of pepsioman.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. pepsioman.com at 0.6 s0.6 s
  2. pepsioman.com at 1.1 s1.1 s
  3. pepsioman.com at 1.7 s1.7 s
  4. pepsioman.com at 2.2 s2.2 s
  5. pepsioman.com at 2.8 s2.8 s
  6. pepsioman.com at 3.3 s3.3 s
  7. pepsioman.com at 3.9 s3.9 s
  8. pepsioman.com at 4.4 s4.4 s

Speed

9 to fix56
  • Use efficient cache lifetimes

    26.0 s · 5.8 MB

    85 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).

  • Improve image delivery

    6.4 s · 1.7 MB

    20 images could be 1.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.4 s faster on a phone.

  • Render-blocking requests

    3.5 s

    12 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.5 s.

  • Reduce unused CSS

    2.7 s · 576 KiB

    About 576 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.7 s faster on a phone.

  • Reduce unused JavaScript

    2.4 s · 617 KiB

    About 617 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.4 s faster on a phone.

  • Minify JavaScript

    2.4 s · 468 KiB

    468 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 56

    56/100

    Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.

  • Minify CSS

    600 ms · 151 KiB

    151 KiB could be saved by minifying CSS.

  • Font display

    350 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).

  • Legacy JavaScript

    250 ms · 29 KiB

    Polyfills for old browsers add 29 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Other Google APIs/SDKs and Google Fonts and others), adding 304 KiB and 141 ms of main-thread time.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 94 ms. During a long task the page ignores taps.

  • Document request latency

    38 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 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.

2 checks passed
  • Main-thread work: 0.9 s

    A phone's processor spends 0.9 s on main-thread work while loading, 309 ms of it running JavaScript. That is comfortably low.

  • Server response: 69 ms

    69 ms

    Your server sent the HTML in 69 ms, well inside Google's 600 ms guideline.

Core Web Vitals

6 to fix67
  • Largest Contentful Paint: 32.3 s

    32.3 s

    Your largest element takes 32.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Customer Call Centre : 24 596 999 العربية Tenders Careers I…”.

  • Time to Interactive: 32.7 s

    32.7 s

    The page becomes fully interactive after 32.7 s. Good is under 3.8 s.

  • Speed Index: 12.7 s

    12.7 s

    Visually, the page fills in at 12.7 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 5.4 s

    5.4 s

    The first text or image appears after 5.4 s on a phone. Good is under 1.8 s.

  • Largest content (LCP) got 29% slower for real visitors

    +29%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.8 s to 3.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • 21 images without width and height

    21 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 104 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.014

    0.014

    The layout barely moves while loading (CLS 0.014, good is under 0.1).

  • Total Blocking Time: 31 ms

    31 ms

    Scripts block the page for only 31 ms while loading. Good is under 200 ms.

Images and page weight

4 to fix43
  • Page weight: 6.1 MB in 104 requests

    6.1 MB

    Your homepage downloads 6.1 MB in 104 requests on a phone: images 4.2 MB (66), scripts 1.2 MB (11) and stylesheets 628 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • 13 images in older formats

    13 images (2.3 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.

  • 8 images below the first screen load straight away

    8 images further down the page (492 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 1 image far larger than shown

    60 KiB

    1 image is downloaded at several times the size a phone draws it, for example 1661412769_Mainbanner02.jpg at 1,200 px wide, shown at 360 px. Resized copies would save about 60 KiB.

  • About 1.7 g of CO₂ per visit

    1.74 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.74 g of CO₂e: 208.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

8 to fixGoogle 7183
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • ARIA input fields must have an accessible name (1 element)

    ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • All page content should be contained by landmarks (27 elements)

    All page content should be contained by landmarks: 27 elements on the page fail this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • 13 links without text

    13 visible links have no text or label, so screen readers cannot say where they go.

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Headings skip levels

    Headings skip levels (h1 → h5), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 27 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 27 passed and 8 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

8 to fixGoogle 7565
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (14 characters)

    Your title is only 14 characters: “OmanrefCo Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 18 H1 headlines

    There are 18 <h1> headlines (“Our Products & brands”, “Welcome to” and “Milestones”). One clear main headline is easier for people and search engines.

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 6 links crawlers can't follow

    6 links have no real href, so search engines can't follow them.

  • 6 links with vague text

    6 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 107 internal links, 8 external

    The homepage links to 107 pages on pepsioman.com and 8 external pages.

2 checks passed
  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://pepsioman.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://pepsioman.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.

2 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.

  • Text is in the HTML

    Your server sends the page's text in the HTML (483 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix88
  • 14 pages share a title

    https://pepsioman.com/tenderform.php, https://pepsioman.com/careers.php, https://pepsioman.com/international-sales.php, https://pepsioman.com/delivery.php, https://pepsioman.com/about.php and https://pepsioman.com/mission-vision.php and 8 others all use the title “OmanrefCo”. 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://pepsioman.com/tenderform.php, https://pepsioman.com/careers.php, https://pepsioman.com/international-sales.php, https://pepsioman.com/delivery.php, https://pepsioman.com/about.php and https://pepsioman.com/mission-vision.php and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 39 found) and read each the way a search engine does.

5 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 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

1 to fixGoogle 9293
  • 12 small tap targets

    12 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 low-resolution images

    3 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • Only about 202 words

    The homepage has only about 202 words of visible text; thin pages give Google and first-time buyers little to go on.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • 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
  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”, “SIGN UP” and “Sign up 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 Analytics.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (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.

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 4 other companies contacted

    Loading the homepage contacts 4 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 pepsioman.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
jQuery
Analytics
Google Analytics
Hosting
InMotion Hosting, Inc.

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 44 issues on pepsioman.com, including 15 speed issues, 8 SEO issues and 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25