Website review, no card needed

saudikayan.com logo

saudikayan.com website review

Visit site (opens in a new tab)Reviewed 27 October 202630 issues · 72 checks

This review found 30 issues worth fixing on saudikayan.com, 12 of them high impact, across 72 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

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

How it loaded on a phone

  1. saudikayan.com at 1.1 s1.1 s
  2. saudikayan.com at 2.1 s2.1 s
  3. saudikayan.com at 3.2 s3.2 s
  4. saudikayan.com at 4.3 s4.3 s
  5. saudikayan.com at 5.4 s5.4 s
  6. saudikayan.com at 6.4 s6.4 s
  7. saudikayan.com at 7.5 s7.5 s
  8. saudikayan.com at 8.6 s8.6 s

Speed

7 to fix33
  • Render-blocking requests

    4.8 s

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

  • Reduce unused CSS

    3.3 s · 668 KiB

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

  • Font display

    1.9 s

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

  • Mobile performance score: 33

    33/100

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

  • Reduce unused JavaScript

    1.2 MB

    About 1.2 MB of JavaScript is downloaded but never used on this page.

  • Google Tag Manager adds 228 ms

    228 ms

    Google Tag Manager costs a phone 228 ms of main-thread work and 307 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.

  • Google CDN adds 141 ms

    141 ms

    Google CDN costs a phone 141 ms of main-thread work and 351 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Analytics and others), adding 682 KiB and 397 ms of main-thread time.

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    27 KiB

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

  • Use efficient cache lifetimes

    16 KiB

    1 file is served with short cache lifetimes, so returning visitors download them again (16 KiB).

  • Document request latency

    10 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 71 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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, 366 ms of it running JavaScript. That is comfortably low.

  • Server response: 227 ms

    227 ms

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

Core Web Vitals

6 to fix37
  • Speed Index: 12.1 s

    12.1 s

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

  • Time to Interactive: 17.0 s

    17.0 s

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

  • First Contentful Paint: 5.1 s

    5.1 s

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

  • Cumulative Layout Shift: 0.606

    0.606

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

  • Largest Contentful Paint: 5.4 s

    5.4 s

    Your largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Saudi Kayan Petrochemical Company (Saudi Kayan) is a Saudi …”. Most of its time is element render delay (5.5 s).

  • Total Blocking Time: 292 ms

    292 ms

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

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

Images and page weight

1 to fix85
  • Page weight: 2.6 MB in 26 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 26 requests on a phone: scripts 1.7 MB (8), stylesheets 682 KiB (2) and fonts 232 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • About 0.7 g of CO₂ per visit

    0.74 g

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

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

2 to fixGoogle 9496
  • 12 text elements with low contrast

    12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 7 images in the HTML carry an alt attribute.

  • 34 automated accessibility rules passed

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

SEO

6 to fixGoogle 8570
  • No meta description

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

  • Title is short (17 characters)

    Your title is only 17 characters: “Saudikayan - 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.

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

  • No XML sitemap

    No XML sitemap at https://saudikayan.com/sitemap.xml, so Google discovers your pages only by following links.

  • 2 links with vague text

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

  • 24 internal links, 0 external

    The homepage links to 24 pages on saudikayan.com and 0 external pages.

3 checks passed
  • One H1 headline

    Your main headline reads: “Welcome to Saudi Kayan”.

  • Canonical URL set

    The canonical URL is https://saudikayan.com/en.

  • robots.txt in place

    robots.txt is in place.

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://saudikayan.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 (301 words), so crawlers that don't run JavaScript still read it.

Other pages

4 to fix78
  • 3 pages share a title

    https://saudikayan.com/en, https://saudikayan.com/ar/CountrySelector and https://saudikayan.com/en/CountrySelector all use the title “Saudikayan - Home”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 15 pages without a meta description

    https://saudikayan.com/en/our-company/vision-mission, https://saudikayan.com/en/our-company/board-of-directors, https://saudikayan.com/en/our-company/executive-team, https://saudikayan.com/en/our-company/contact-us, https://saudikayan.com/en/environment-safety and https://saudikayan.com/en/products and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 2 links to non-canonical URLs

    Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://saudikayan.com/ar/CountrySelector, whose canonical is https://saudikayan.com/en. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://saudikayan.com/en/news has no <h1> headline, so visitors and search engines get no clear main topic.

  • 6 pages slow to respond

    https://saudikayan.com/en/our-company/board-of-directors, https://saudikayan.com/en/our-company/contact-us, https://saudikayan.com/en/environment-safety, https://saudikayan.com/en/products, https://saudikayan.com/ar/CountrySelector and https://saudikayan.com/en/CountrySelector took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 18 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

Google 100100
  • Missing source maps

    Large scripts ship without source maps.

3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • 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.

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

    The homepage carries about 256 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US”.

  • 3 calls to action

    The homepage has 3 calls to action, for example “Contact Us”.

  • 2 short forms

    2 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager.

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.

  • 9 cookies set on arrival

    9

    Opening the homepage sets 9 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 saudikayan.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Analytics
Google Tag Manager
Hosting
As6453 Tata Communications America Inc

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on saudikayan.com, including 13 speed issues, 6 SEO 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