Programmable

Website review, no card needed

v2.sa logo

v2.sa website review

Visit site (opens in a new tab)Reviewed 24 October 202615 issues · 82 checks

This review found 15 issues worth fixing on v2.sa, 5 of them high impact, across 82 checks. The most urgent: hidden but focusable. 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

Site score

87B

Closest competitors among reviewed websites

Compare side by side

One score from every part of this review. How it works

v2.sa (opens in a new tab)
Full-page screenshot of v2.sa (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

v2.sa does not allow embedding, so this is Google's rendering of the page.

Speed

2 to fix84

  • Reduce unused CSS

    1.1 MB

    About 1.1 MB of CSS is downloaded but never applied on this page.

  • Mobile performance score: 84

    84/100

    Your mobile performance score is 84 (desktop: 99). Pages that score under 90 lose visitors before the first paint.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 110 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    55 KiB

    17 files are served with short cache lifetimes, so returning visitors download them again (55 KiB).

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

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

  • Server response: 169 ms

    169 ms

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

Core Web Vitals

1 to fix79

  • Cumulative Layout Shift: 0.322

    0.322

    The layout shifts by 0.322 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

5 checks passed

  • Speed Index: 2.9 s

    2.9 s

    Visually, the page fills in at 2.9 s (Speed Index), inside the 3.4 s “good” threshold.

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Your trusted partner in cloud services”.

  • Total Blocking Time: 37 ms

    37 ms

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

  • Time to Interactive: 1.3 s

    1.3 s

    The page is fully interactive after 1.3 s.

Images and page weight

1 to fix97

  • An image on the first screen is lazy-loaded

    vv_logo-02-1.png 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 0.5 g of CO₂ per visit

    0.49 g

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

3 checks passed

  • Page weight: 1.7 MB in 51 requests

    1.7 MB

    Your homepage downloads 1.7 MB in 51 requests on a phone: other files 1.2 MB (33), fonts 402 KiB (11) and images 137 KiB (3). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

5 to fixGoogle 9791

  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

    All page content should be contained by landmarks: 63 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.

  • ARIA role should be appropriate for the element (1 element)

    ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed

  • Every image has alt text

    All 41 images in the HTML carry an alt attribute.

  • 35 automated accessibility rules passed

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

SEO

Google 100100

  • 79 internal links, 6 external

    The homepage links to 79 pages on v2.sa and 6 external pages.

8 checks passed

  • Meta description: 115 characters

    Your meta description is 115 characters: “A leading provider of cloud services in the Kingdom. We provide innovative ICT cloud solutions to help you succeed.”.

  • One H1 headline

    Your main headline reads: “V2 Public Cloud”.

  • Title: 49 characters

    Your title is a healthy 49 characters: “V2 Cloud | Leading Cloud Services in Saudi Arabia”.

  • Canonical URL set

    The canonical URL is https://v2.sa/.

  • Structured data in place

    Structured data found: ImageObject, Organization, Person, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://v2.sa/sitemap_index.xml.

AI search readiness

100

  • No llms.txt

    There is no /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: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.

  • Text is in the HTML

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

Other pages

100

  • 1 page with very little text

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

  • 15 internal pages checked

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

7 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 a meta description

    All 15 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 15 pages that loaded have a <title>.

Best practices

Google 96100

  • 1 low-resolution image

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

Security and trust

3 to fix71

  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://v2.sa/cdn-cgi/l/email-protection (404).

  • http:// does not redirect

    http://v2.sa does not redirect to https, so some visitors land on the insecure version.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • Short HSTS lifetime

    HSTS is set, but max-age is 0 days; one year is the recommended minimum.

  • 1 link through redirect chains

    1 link go through two or more redirects, for example https://ruh.cld.v2.sa/.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block;”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

4 checks passed

  • Served over HTTPS

    The homepage is served over HTTPS (v2.sa).

  • Valid certificate (63 days left)

    The certificate from Google Trust Services · WE1 verifies for v2.sa and is valid for another 63 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • HTTP/2

    The server speaks HTTP/2, so browsers load many files over one connection.

Domain and trust

  • No CAA record

    v2.sa has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

Content and conversion

2 to fix79

  • 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 opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 484 words of copy

    The homepage carries about 484 words of visible text.

5 checks passed

  • 2 calls to action

    The homepage has 2 calls to action, for example “contact” and “Contact us!”.

  • Social proof on the page

    Social proof on the homepage: 33 testimonial or review blocks and 30 customer or partner logos.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Email authentication

100

  • Email authentication score: 100/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed

  • DMARC policy: reject

    DMARC tells receivers to reject mail that fails authentication, and sends you reports.

  • SPF with a strict ending (-all)

    An SPF record lists your sending servers and tells receivers to reject anything else: “v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net -all”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”, “selector2” and “k2”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads 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.

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

  • 1 other company contacted

    Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Upkeep, stack and company

  • The footer still says © 2024.
  • It runs WordPress 6.8.2; the current release is 7.1.3.
  • 4 plugins are behind their latest release.contact-form-7 6.1.1 → 6.2.2 · embedpress 4.3.1 → 4.7.0 · metform 4.0.6 → 4.3.3 · elementskit-lite 3.7.2 → 4.0.9

Stack

CMS
WordPress 6.8.2
Framework
jQuery
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 15 issues on v2.sa, including 3 speed issues and 2 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