Website review, no card needed
alfahhad.sa website review
Visit site (opens in a new tab)Reviewed 19 October 202654 issues · 88 checks
This review found 54 issues worth fixing on alfahhad.sa, 23 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
59FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 5.4 s |
| May 2, 2026 | 5.3 s |
| May 9, 2026 | 6.0 s |
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 5.6 s |
| May 30, 2026 | 5.7 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 6.0 s |
| Jun 20, 2026 | 6.4 s |
| Jun 27, 2026 | 6.3 s |
| Jul 4, 2026 | 6.3 s |
| Jul 11, 2026 | 6.2 s |
| Jul 18, 2026 | 6.1 s |
| Jul 25, 2026 | 6.3 s |
| Aug 1, 2026 | 6.5 s |
| Aug 8, 2026 | 6.6 s |
| Aug 15, 2026 | 6.7 s |
| Aug 22, 2026 | 6.5 s |
| Aug 29, 2026 | 6.5 s |
| Sep 5, 2026 | 6.1 s |
| Sep 12, 2026 | 6.3 s |
| Sep 19, 2026 | 6.6 s |
| Oct 3, 2026 | 4.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 101 ms |
| May 2, 2026 | 95 ms |
| May 9, 2026 | 93 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 107 ms |
| May 30, 2026 | 112 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 101 ms |
| Jun 20, 2026 | 90 ms |
| Jun 27, 2026 | 82 ms |
| Jul 4, 2026 | 91 ms |
| Jul 11, 2026 | 94 ms |
| Jul 18, 2026 | 90 ms |
| Jul 25, 2026 | 102 ms |
| Aug 1, 2026 | 90 ms |
| Aug 8, 2026 | 90 ms |
| Aug 15, 2026 | 90 ms |
| Aug 22, 2026 | 92 ms |
| Aug 29, 2026 | 97 ms |
| Sep 5, 2026 | 96 ms |
| Sep 12, 2026 | 97 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
Speed
Use efficient cache lifetimes
13.3 s · 12.6 MB68 files are served with short cache lifetimes, so returning visitors download them again (12.6 MB).
Improve image delivery
3.0 s · 2.2 MB14 images could be 2.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Render-blocking requests
2.9 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Reduce unused JavaScript
1.6 s · 420 KiBAbout 420 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.5 s · 246 KiBAbout 246 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Font display
1.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 81). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (autofaucet.org, Google Tag Manager and Google Maps and others), adding 786 KiB and 575 ms of main-thread time.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Legacy JavaScript
300 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
autofaucet.org adds 271 ms
271 msautofaucet.org costs a phone 271 ms of main-thread work and 270 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.
Minify CSS
150 ms · 37 KiB37 KiB could be saved by minifying CSS.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.
Minify JavaScript
31 KiB31 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 81 but mobile only 32. 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: 271 ms
271 msYour server sent the HTML in 271 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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: 30.7 s
30.7 sYour largest element takes 30.7 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: 31.4 s
31.4 sThe page becomes fully interactive after 31.4 s. Good is under 3.8 s.
Speed Index: 13.9 s
13.9 sVisually, the page fills in at 13.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.393
0.393The layout shifts by 0.393 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user LCP: 3.6 s
3.6 sReal visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.2 s
2.2 sReal visitors see the first content after 2.2 s (75th percentile). Good is under 1.8 s.
20 images without width and height
20 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 278 ms
278 msScripts block taps and scrolling for 278 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 101 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 5.4 s to 4.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user CLS: 0.08
0.08For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 20.3 MB in 126 requests
20.3 MBYour homepage downloads 20.3 MB in 126 requests on a phone: media 13.7 MB (2), images 4.7 MB (25) and scripts 1.2 MB (47). Under 2 MB keeps phones on slow connections fast.
11 images in older formats
11 images (1.5 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.
6 images below the first screen load straight away
6 images further down the page (860 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.7 g of CO₂ per visit
5.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.74 g of CO₂e: 689.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
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.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (9 elements)
All page content should be contained by landmarks: 9 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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
3 links without text
3 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h4, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
24 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 24 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (24 characters)
Your title is only 24 characters: “شركة الفهاد-مساهمة مقفلة”. 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.
4 H1 headlines
There are 4 <h1> headlines (“فهاد بن سليمان الفهاد”, “عبد الله بن أحمد الفهاد” and “خالد بن عبدالله الناصر”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
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://alfahhad.sa/sitemap.xml, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
41 internal links, 5 external
The homepage links to 41 pages on alfahhad.sa and 5 external pages.
1 checks passed
robots.txt in place
robots.txt is in place.
AI search readiness
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://alfahhad.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 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
1 linked page is broken
Your homepage links to https://alfahhad.sa/blog.aspx, which answers with an error. Visitors hit a dead end and search engines drop it.
13 pages share a title
/, https://alfahhad.sa/jobs.aspx, https://alfahhad.sa/Services.aspx, https://alfahhad.sa/Blogs.aspx, https://alfahhad.sa/media.aspx and https://alfahhad.sa/Contact.aspx and 7 others all use the title “شركة الفهاد-مساهمة مقفلة”. Search engines can't tell which page to show for a search, so each competes with the others.
14 pages without a meta description
https://alfahhad.sa/en/Defaulten.aspx, https://alfahhad.sa/jobs.aspx, https://alfahhad.sa/About.aspx, https://alfahhad.sa/Services.aspx, https://alfahhad.sa/Blogs.aspx and https://alfahhad.sa/media.aspx and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://alfahhad.sa/jobs.aspx, https://alfahhad.sa/About.aspx, https://alfahhad.sa/Services.aspx, https://alfahhad.sa/Blogs.aspx, https://alfahhad.sa/media.aspx and https://alfahhad.sa/Contact.aspx and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages with very little text
https://alfahhad.sa/jobs.aspx, https://alfahhad.sa/About.aspx, https://alfahhad.sa/Services.aspx, https://alfahhad.sa/media.aspx, https://alfahhad.sa/Contact.aspx and https://alfahhad.sa/community.aspx and 6 others 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.
15 internal pages checked
We fetched 15 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
6 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 43 words
The homepage has only about 43 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 (0 fields at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before 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.
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 alfahhad.sa, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2019.
Stack
- Framework
- jQuery
Company
- Headquarters
- Riyadh
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 54 issues on alfahhad.sa, including 21 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.