Website review, no card needed
maharah.com website review
Visit site (opens in a new tab)Reviewed 3 November 202629 issues · 64 checks
This review found 29 issues worth fixing on maharah.com, 15 of them high impact, across 64 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 7.8 s |
| May 23, 2026 | 7.5 s |
| May 30, 2026 | 7.2 s |
| Jun 6, 2026 | 7.1 s |
| Jun 13, 2026 | 7.4 s |
| Jun 20, 2026 | 7.8 s |
| Jun 27, 2026 | 8.3 s |
| Jul 4, 2026 | 8.7 s |
| Jul 11, 2026 | 8.6 s |
| Jul 18, 2026 | 8.7 s |
| Jul 25, 2026 | 8.3 s |
| Aug 1, 2026 | 7.9 s |
| Aug 8, 2026 | 7.7 s |
| Aug 15, 2026 | 7.4 s |
| Aug 22, 2026 | 7.5 s |
| Aug 29, 2026 | 7.4 s |
| Sep 5, 2026 | 7.3 s |
| Sep 12, 2026 | 7.3 s |
| Sep 19, 2026 | 7.2 s |
| Sep 26, 2026 | 6.8 s |
| Oct 3, 2026 | 6.5 s |
| Oct 10, 2026 | 6.2 s |
| Oct 17, 2026 | 5.9 s |
| Oct 24, 2026 | 5.7 s |
| Oct 31, 2026 | 5.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 182 ms |
| May 23, 2026 | 181 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 181 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 186 ms |
| Jul 4, 2026 | 190 ms |
| Jul 11, 2026 | 194 ms |
| Jul 18, 2026 | 192 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 187 ms |
| Aug 8, 2026 | 183 ms |
| Aug 15, 2026 | 183 ms |
| Aug 22, 2026 | 187 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 190 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 196 ms |
| Sep 26, 2026 | 200 ms |
| Oct 3, 2026 | 197 ms |
| Oct 10, 2026 | 190 ms |
| Oct 17, 2026 | 190 ms |
| Oct 24, 2026 | 199 ms |
| Oct 31, 2026 | 210 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 5.6 s
5.6 sReal visitors wait 5.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 4.6 s
4.6 sReal visitors see the first content after 4.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.4 s
2.4 sReal visitors wait 2.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Real-user INP: 211 ms
211 msReal visitors wait 211 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 182 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 7.8 s to 5.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 4.6 MB
4.6 MBYour homepage downloads 4.6 MB on a phone, 1.7 MB of it images (37%). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
Certification_Badge.png weighs 1.0 MB. On a phone connection a single image that size takes seconds.
3 images in older formats
3 images (1.2 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.
2 images below the first screen load straight away
2 images further down the page (50 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.3 g of CO₂ per visit
1.30 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.30 g of CO₂e: 155.8 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
Certain ARIA roles must be contained by particular parents (3 elements)
Certain ARIA roles must be contained by particular parents: 3 elements on the page fail this check, rated critical by axe-core.
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Orphan list items
Some list items are not inside a list.
15 images without alt text
15 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
4 H1 headlines
There are 4 <h1> headlines (“خلف كل نجاح”, “خلف كل نجاح” and “خلف كل نجاح”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (BreadcrumbList, Organization, WebPage and WebSite) but with 1 problem, for example “Organization: logo is not an absolute URL ("https://maharah.com/wp-content/uploads/2021/08/logo.svg")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
61 internal links, 21 external
The homepage links to 61 pages on maharah.com and 21 external pages.
5 checks passed
Meta description: 140 characters
Your meta description is 140 characters: “هل تبحث عن أفضل شركة استقدام عمالة أو توظيفها مباشرة؟ في مهارة نوفر لكم خدمات لقطاع الافراد وقطاع الأعمال، ونلبي طلبات …”.
Title: 65 characters
Your title is a healthy 65 characters: “أفضل شركة استقدام عمالة أو توظيفها مباشرة - مهارة للموارد البشرية”.
Canonical URL set
The canonical URL is https://maharah.com/.
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://maharah.com/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://maharah.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.
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.
Other pages
12 pages without a meta description
https://maharah.com/about-us, https://maharah.com/board-of-directors, https://maharah.com/president-message, https://maharah.com/executives, https://maharah.com/subsidiaries and https://maharah.com/investors and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://maharah.com/president-message, whose canonical is https://maharah.com/en/president-message. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages with very little text
https://maharah.com/about-us, https://maharah.com/board-of-directors, https://maharah.com/president-message, https://maharah.com/executives, https://maharah.com/subsidiaries and https://maharah.com/investors and 5 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.
9 pages slow to respond
https://maharah.com/about-us, https://maharah.com/president-message, https://maharah.com/executives, https://maharah.com/governance, https://maharah.com/annual-report and https://maharah.com/%D9%81%D8%B1%D9%88%D8%B9%D9%86%D8%A7 and 3 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
5 checks passed
Linked pages load
12 pages of 15 loaded without an error (the rest turned automated requests away).
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 12 pages that loaded have a <title>.
Best practices
11 small tap targets
11 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
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.
Only about 49 words
The homepage has only about 49 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.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
4 checks passed
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 2 customer or partner logos and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel, Microsoft Clarity, LinkedIn Insight and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 4 mores (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.
21 cookies set on arrival
21Opening the homepage sets 21 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.
38 other companies contacted
Loading the homepage contacts 38 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 maharah.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
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on maharah.com, including 5 speed issues, 3 SEO issues and 3 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.