Website review, no card needed

wafrainv.com logo

wafrainv.com website review

Visit site (opens in a new tab)Reviewed 19 October 202644 issues · 75 checks

This review found 44 issues worth fixing on wafrainv.com, 20 of them high impact, across 75 checks. The most urgent: render-blocking requests. 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
3.9 s3.4 sSep 12Oct 33.4 s
Show as table
DateReal-visitor load time (LCP)
Sep 12, 20263.9 s
Sep 19, 20263.8 s
Sep 26, 20263.7 s
Oct 3, 20263.4 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

Full-page screenshot of wafrainv.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wafrainv.com at 0.6 s0.6 s
  2. wafrainv.com at 1.2 s1.2 s
  3. wafrainv.com at 1.9 s1.9 s
  4. wafrainv.com at 2.5 s2.5 s
  5. wafrainv.com at 3.1 s3.1 s
  6. wafrainv.com at 3.7 s3.7 s
  7. wafrainv.com at 4.3 s4.3 s
  8. wafrainv.com at 5.0 s5.0 s

Speed

11 to fix45
  • Render-blocking requests

    7.2 s

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

  • Use efficient cache lifetimes

    2.4 s · 2.4 MB

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

  • Reduce unused JavaScript

    1.6 s · 390 KiB

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

  • Reduce unused CSS

    1.2 s · 214 KiB

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

  • Mobile performance score: 45

    45/100

    Your mobile performance score is 45 (desktop: 53). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Improve image delivery

    250 ms · 5.3 MB

    24 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • 6 long tasks on the main thread

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

  • Font display

    400 ms

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

  • Minify CSS

    300 ms · 38 KiB

    38 KiB could be saved by minifying CSS.

  • Main-thread work: 3.1 s

    A phone's processor spends 3.1 s on main-thread work while loading, 758 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Google Maps adds 224 ms

    224 ms

    Google Maps costs a phone 224 ms of main-thread work and 388 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.

  • 6 third-party services on the page

    6 third-party services load with your homepage (Google Maps, Google Tag Manager and Cloudflare CDN and others), adding 622 KiB and 500 ms of main-thread time.

  • Minify JavaScript

    34 KiB

    34 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    23 KiB

    Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need.

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

1 checks passed
  • Server response: 224 ms

    224 ms

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

Core Web Vitals

10 to fix50
  • 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: 21.0 s

    21.0 s

    Your largest element takes 21.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 43.8 s

    43.8 s

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

  • Speed Index: 13.8 s

    13.8 s

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

  • First Contentful Paint: 6.5 s

    6.5 s

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

  • Real-user LCP: 3.4 s

    3.4 s

    Real visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user FCP: 2.7 s

    2.7 s

    Real visitors see the first content after 2.7 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 1.0 s

    1.0 s

    Real visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.

  • Total Blocking Time: 436 ms

    436 ms

    Scripts block taps and scrolling for 436 ms in total while the page loads. Good is under 200 ms.

  • 2 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

2 checks passed
  • Real-user CLS: 0.04

    0.04

    For real visitors the layout shifts by 0.04 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix14
  • Page weight: 19.2 MB in 166 requests

    19.2 MB

    Your homepage downloads 19.2 MB in 166 requests on a phone: images 17.5 MB (42), scripts 1.0 MB (53) and stylesheets 379 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • 11 images over 500 KB

    11 images weigh 11.1 MB together. On a phone connection a single image that size takes seconds.

  • 15 images far larger than shown

    3.7 MB

    15 images are downloaded at several times the size a phone draws them, for example 11.jpg at 1,920 px wide, shown at 360 px. Resized copies would save about 3.7 MB.

  • 32 images in older formats

    32 images (16.9 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.

  • An image on the first screen is lazy-loaded

    2P0A3055-768x512.jpg 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 5.4 g of CO₂ per visit

    5.44 g

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

Accessibility

4 to fix91
  • 1 button without a name

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

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • 6 links without text

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

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.

SEO

5 to fixGoogle 8572
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No social preview image

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

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

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

  • 79 internal links, 4 external

    The homepage links to 79 pages on wafrainv.com and 4 external pages.

4 checks passed
  • Title: 52 characters

    Your title is a healthy 52 characters: “Wafra Investment – Wafra International Investment Co”.

  • Canonical URL set

    The canonical URL is https://wafrainv.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix83
  • 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://wafrainv.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.

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

3 to fixGoogle 6976
  • 2 broken images

    2 images failed to load on a phone, for example https://wafrainv.com/wp-content/themes/homesweet/images/logo-white.png.

  • 5 JavaScript errors while loading

    5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 16 distorted images

    16 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    16 of 16 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix57
  • 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.

  • No calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 14 words

    The homepage has only about 14 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.

3 checks passed
  • 1 short form

    A short form (2 fields at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 5 customer or partner logos and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 6 other companies contacted

    Loading the homepage contacts 6 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 wafrainv.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
WordPress
Framework
React
Analytics
Google Analytics

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 wafrainv.com, including 21 speed issues, 5 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