Website review, no card needed

arabianfal.com logo

arabianfal.com website review

Visit site (opens in a new tab)Reviewed 25 October 202646 issues · 91 checks

This review found 46 issues worth fixing on arabianfal.com, 19 of them high impact, across 91 checks. The most urgent: improve image delivery. 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.0 sMay 2Oct 173.7 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20263.5 s
May 9, 20263.5 s
May 16, 20263.4 s
May 23, 20263.3 s
May 30, 20263.3 s
Jun 6, 20263.3 s
Jun 13, 20263.4 s
Jun 20, 20263.3 s
Jun 27, 20263.2 s
Jul 4, 20263.2 s
Jul 11, 20263.1 s
Jul 18, 20263.2 s
Jul 25, 20263.3 s
Aug 1, 20263.4 s
Aug 8, 20263.4 s
Aug 15, 20263.5 s
Aug 22, 20263.4 s
Aug 29, 20263.5 s
Sep 5, 20263.5 s
Sep 12, 20263.6 s
Sep 19, 20263.8 s
Sep 26, 20263.8 s
Oct 3, 20263.8 s
Oct 10, 20263.7 s
Oct 17, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
207 ms129 msMay 2Oct 17143 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026171 ms
May 9, 2026163 ms
May 16, 2026184 ms
May 23, 2026177 ms
May 30, 2026183 ms
Jun 6, 2026198 ms
Jun 13, 2026178 ms
Jun 20, 2026163 ms
Jun 27, 2026162 ms
Jul 4, 2026148 ms
Jul 11, 2026143 ms
Jul 18, 2026150 ms
Jul 25, 2026151 ms
Aug 1, 2026155 ms
Aug 8, 2026162 ms
Aug 15, 2026154 ms
Aug 22, 2026155 ms
Aug 29, 2026147 ms
Sep 5, 2026146 ms
Sep 12, 2026144 ms
Sep 19, 2026142 ms
Sep 26, 2026144 ms
Oct 3, 2026138 ms
Oct 10, 2026139 ms
Oct 17, 2026143 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 arabianfal.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. arabianfal.com at 0.4 s0.4 s
  2. arabianfal.com at 0.9 s0.9 s
  3. arabianfal.com at 1.3 s1.3 s
  4. arabianfal.com at 1.7 s1.7 s
  5. arabianfal.com at 2.2 s2.2 s
  6. arabianfal.com at 2.6 s2.6 s
  7. arabianfal.com at 3.0 s3.0 s
  8. arabianfal.com at 3.5 s3.5 s

Speed

9 to fix55
  • Improve image delivery

    1.4 s · 2.1 MB

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

  • Reduce unused JavaScript

    2.9 s · 665 KiB

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

  • Render-blocking requests

    3.3 s

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

  • 3,512 HTML elements

    The page has 3,512 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused CSS

    900 ms · 195 KiB

    About 195 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (YouTube, elementor.com and Other Google APIs/SDKs and others), adding 1.1 MB and 451 ms of main-thread time.

  • YouTube adds 406 ms

    406 ms

    YouTube costs a phone 406 ms of main-thread work and 977 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.

  • Main-thread work: 2.2 s

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

  • 6 long tasks on the main thread

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

  • Font display

    50 ms

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

  • Use efficient cache lifetimes

    16 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 94 but mobile only 55. 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.

  • 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: 39 ms

    39 ms

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

Core Web Vitals

9 to fix67
  • 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.

  • Real-user FCP: 3.4 s

    3.4 s

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

  • Real-user TTFB: 2.0 s

    2.0 s

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

  • First Contentful Paint: 11.5 s

    11.5 s

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

  • Largest Contentful Paint: 24.8 s

    24.8 s

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

  • Time to Interactive: 26.4 s

    26.4 s

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

  • Speed Index: 11.6 s

    11.6 s

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

  • Real-user LCP: 4.0 s

    4.0 s

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

  • 57 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    +4%

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

5 checks passed
  • Real-user INP: 167 ms

    167 ms

    Real visitors wait 167 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.01

    0.01

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

  • Tap response (INP) got 16% faster for real visitors

    -16%

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

  • Total Blocking Time: 74 ms

    74 ms

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

  • Cumulative Layout Shift: 0.008

    0.008

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

Images and page weight

5 to fix18
  • Page weight: 5.9 MB in 159 requests

    5.9 MB

    Your homepage downloads 5.9 MB in 159 requests on a phone: images 3.8 MB (64), scripts 1.3 MB (47) and fonts 348 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    arabianfal-26-1.jpg weighs 513 KiB. On a phone connection a single image that size takes seconds.

  • 3 images far larger than shown

    566 KiB

    3 images are downloaded at several times the size a phone draws them, for example arabianfal-26-1.jpg at 1,270 px wide, shown at 394 px. Resized copies would save about 566 KiB.

  • 13 images below the first screen load straight away

    13 images further down the page (2.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • 8 images in older formats

    8 images (2.0 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.

  • About 1.7 g of CO₂ per visit

    1.67 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.67 g of CO₂e: 199.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 8490
  • 4 text elements with low contrast

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

  • Frames without titles

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

  • 8 images without alt text

    8 images have no alt text, which hurts accessibility and image search.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

  • 23 links without text

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

  • 9 form fields without a label

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

  • Alternative text of images should not be repeated as text (2 elements)

    Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 49 automated accessibility rules passed

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

SEO

4 to fixGoogle 6980
  • No meta description

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

  • Title is short (22 characters)

    Your title is only 22 characters: “Homepage - Arabian Fal”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 3 links crawlers can't follow

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

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 84 internal links, 2 external

    The homepage links to 84 pages on arabianfal.com and 2 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “43+ Years Of Experience in the Energy Sector”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, 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://arabianfal.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://arabianfal.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.

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: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix85
  • 14 pages without a meta description

    https://arabianfal.com/careers-3-2, https://arabianfal.com/%d8%b4%d8%b1%d9%83%d8%a9-%d9%81%d8%a7%d9%84-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9-%d8%aa%d9%81%d8%aa%d8%aa%d8%ad-%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%aa%d8%b7%d9%88%d9%8a%d8%b1-%d8%a7%d9%84, https://arabianfal.com/arabian-fal-announced-local-workforce-development-center, https://arabianfal.com/%d8%b4%d8%b1%d9%83%d8%a9-%d9%81%d8%a7%d9%84-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9-%d8%aa%d8%b4%d8%a7%d8%b1%d9%83-%d9%83%d8%b1%d8%a7%d8%b9%d9%8a-%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a-%d9%81%d9%8a-%d9%85, https://arabianfal.com/arabian-fal-company-participates-as-a-main-sponsor-at-the-job-fair-2023 and https://arabianfal.com/blog and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 links to non-canonical URLs

    Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://arabianfal.com/%d8%b4%d8%b1%d9%83%d8%a9-%d9%81%d8%a7%d9%84-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9-%d8%aa%d9%81%d8%aa%d8%aa%d8%ad-%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%aa%d8%b7%d9%88%d9%8a%d8%b1-%d8%a7%d9%84, whose canonical is https://arabianfal.com/ar/%D8%B4%D8%B1%D9%83%D8%A9-%D9%81%D8%A7%D9%84-%D8%A7%D9%84%D8%B9%D8%B1%D8%A8%D9%8A%D8%A9-%D8%AA%D9%81%D8%AA%D8%AA%D8%AD-%D9%85%D8%B1%D9%83%D8%B2-%D8%A7%D9%84%D8%AA%D8%B7%D9%88%D9%8A%D8%B1-%D8%A7%D9%84. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 1 page without an H1

    https://arabianfal.com/%d8%a7%d9%84%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a%d8%a9 has no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages with very little text

    https://arabianfal.com/%d8%b4%d8%b1%d9%83%d8%a9-%d9%81%d8%a7%d9%84-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9-%d8%aa%d9%81%d8%aa%d8%aa%d8%ad-%d9%85%d8%b1%d9%83%d8%b2-%d8%a7%d9%84%d8%aa%d8%b7%d9%88%d9%8a%d8%b1-%d8%a7%d9%84, https://arabianfal.com/%d8%b4%d8%b1%d9%83%d8%a9-%d9%81%d8%a7%d9%84-%d8%a7%d9%84%d8%b9%d8%b1%d8%a8%d9%8a%d8%a9-%d8%aa%d8%b4%d8%a7%d8%b1%d9%83-%d9%83%d8%b1%d8%a7%d8%b9%d9%8a-%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a-%d9%81%d9%8a-%d9%85 and https://arabianfal.com/careers have 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.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 14 pages we checked loaded without an error.

  • Titles are unique

    Every page we checked has its own title.

  • 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

3 to fixGoogle 7385
  • 5 third-party cookies

    5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 2 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'setSettings')”.

  • Browser-reported issues

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

1 checks passed
  • 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.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • A 8-field form

    Your longest form asks for 8 fields (8 required). Every extra field lowers completion.

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

  • About 729 words of copy

    The homepage carries about 729 words of visible text.

4 checks passed
  • 13 calls to action

    The homepage has 13 calls to action, for example “Careers – Apply Resume” and “Learn more”.

  • Social proof on the page

    Social proof on the homepage: 8 customer or partner logos and 7 trust badges.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

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

  • 1 cookie set on arrival

    1

    Opening the homepage sets 1 cookie, 1 of them by other companies (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.

  • 11 other companies contacted

    Loading the homepage contacts 11 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 arabianfal.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
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on arabianfal.com, including 18 speed issues, 4 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