karrda.gov.sa website review

• Use efficient cache lifetimes

  7.7 s · 7.6 MB

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

• Improve image delivery

  1.0 s · 5.7 MB

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

  Show on pageElements (3)

• Render-blocking requests

  3.2 s

  1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 3.2 s.

• Reduce unused CSS

  2.5 s · 406 KiB

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

• Reduce unused JavaScript

  1.8 s · 339 KiB

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

• Mobile performance score: 58

  58/100

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

• openwidget.com adds 53 ms

  53 ms

  openwidget.com costs a phone 53 ms of main-thread work and 338 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.

• 3 third-party services on the page

  3 third-party services load with your homepage (userway.org, openwidget.com and Cloudflare CDN), adding 533 KiB and 140 ms of main-thread time.

• 4 long tasks on the main thread

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

• Legacy JavaScript

  11 KiB

  Polyfills for old browsers add 11 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.

• 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: 13.6 s

  13.6 s

  Your largest element takes 13.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load duration (6.5 s).

  Show on pageElements (1)

• Speed Index: 19.2 s

  19.2 s

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

• Time to Interactive: 24.0 s

  24.0 s

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

• First Contentful Paint: 3.8 s

  3.8 s

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

• Real-user LCP: 3.1 s

  3.1 s

  Real visitors wait 3.1 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: 866 ms

  866 ms

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

• 13 images without width and height

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

  Show on pageElements (3)

• Tap response (INP) held steady for real visitors

  +1%

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

• Largest content (LCP) held steady for real visitors

  -3%

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

• Page weight: 8.2 MB in 80 requests

  8.2 MB

  Your homepage downloads 8.2 MB in 80 requests on a phone: images 6.2 MB (28), scripts 1.1 MB (24) and stylesheets 450 KiB (3). Under 2 MB keeps phones on slow connections fast.

• 2 images over 500 KB

  2 images weigh 1.8 MB together. On a phone connection a single image that size takes seconds.

  Elements (2)

• 4 images far larger than shown

  1.4 MB

  4 images are downloaded at several times the size a phone draws them, for example menu-DheRTfaJ.png at 1,024 px wide, shown at 50 px. Resized copies would save about 1.4 MB.

  Elements (4)

• 3 images in older formats

  3 images (1.8 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.

  Elements (3)

• 1 image below the first screen load straight away

  1 image further down the page (70 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  Elements (1)

• About 2.3 g of CO₂ per visit

  2.33 g

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

Not measured in this review.

• No H1 headline

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

• Meta description is long (181 characters)

  Your meta description is 181 characters; Google truncates after about 160, so the end of your pitch is cut.

  View source

• No XML sitemap

  No XML sitemap at https://dev.karrda.gov.sa/sitemap.xml, so Google discovers your pages only by following links.

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No llms.txt

  There is no https://karrda.gov.sa/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 broken image

  1 image failed to load on a phone, for example https://karrda.gov.sa/theme-images/default-imgs/hero-img.png.

• 2 JavaScript errors while loading

  2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Missing source maps

  Large scripts ship without source maps.

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

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

• No form on the homepage

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

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

• 1 cookie set on arrival

  1

  Opening the homepage sets 1 cookie (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.