Website review, no card needed
alwafaagroup.com website review
Visit site (opens in a new tab)Reviewed 22 October 202621 issues · 78 checks
This review found 21 issues worth fixing on alwafaagroup.com, 7 of them high impact, across 78 checks. The most urgent: fails Core Web Vitals for real visitors. 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
90AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.2 s |
| May 9, 2026 | 2.2 s |
| May 16, 2026 | 2.4 s |
| May 23, 2026 | 2.2 s |
| Jun 13, 2026 | 1.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.4 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 118 ms |
| Aug 1, 2026 | 120 ms |
| Aug 8, 2026 | 127 ms |
| Aug 15, 2026 | 147 ms |
| Aug 22, 2026 | 147 ms |
| Aug 29, 2026 | 145 ms |
| Oct 3, 2026 | 145 ms |
| Oct 10, 2026 | 160 ms |
| Oct 17, 2026 | 159 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
How it loaded on a phone
0.6 s
1.2 s
1.8 s
2.3 s
2.9 s
3.5 s
4.1 s
4.7 s
Speed
Mobile performance score: 71
71/100Your mobile performance score is 71 (desktop: 100). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
450 ms · 84 KiBAbout 84 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Legacy JavaScript
300 ms · 24 KiBPolyfills for old browsers add 24 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Cloudflare and Google/Doubleclick Ads and others), adding 207 KiB and 175 ms of main-thread time.
Use efficient cache lifetimes
157 KiB8 files are served with short cache lifetimes, so returning visitors download them again (157 KiB).
Render-blocking requests
150 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Improve image delivery
43 KiB2 images could be 43 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Phones get a much slower page than desktops
Desktop scores 100 but mobile only 71. 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.8 s
A phone's processor spends 0.8 s on main-thread work while loading, 404 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 5.5 s
5.5 sYour largest element takes 5.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Dubai business district skyline”.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) got 35% slower for real visitors
+35%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 119 ms to 159 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 1.9 s
1.9 sReal visitors see the first content after 1.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.1 s
1.1 sReal visitors wait 1.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 5.5 s
5.5 sThe page becomes fully interactive after 5.5 s. Good is under 3.8 s.
Speed Index: 4.5 s
4.5 sVisually, the page fills in at 4.5 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.2 s to 2.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user LCP: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 85 ms
85 msScripts block the page for only 85 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
About 0.2 g of CO₂ per visit
0.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.20 g of CO₂e: 23.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 706 KiB in 44 requests
706 KiBYour homepage downloads 706 KiB in 44 requests on a phone: scripts 374 KiB (16), images 164 KiB (8) and other files 63 KiB (16). That is a lean page.
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
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
21 text elements with low contrast
21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
12 links with vague text
12 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
69 internal links, 11 external
The homepage links to 69 pages on alwafaagroup.com and 11 external pages.
8 checks passed
Meta description: 134 characters
Your meta description is 134 characters: “24 years, 5,000+ UAE clients — AI-powered websites, mobile apps & custom software for Dubai businesses. Get a free cons…”.
One H1 headline
Your main headline reads: “AI-Driven IT & Digital Solutionsfor UAE Businesses”.
Title: 53 characters
Your title is a healthy 53 characters: “AI-Driven IT & Digital Solutions UAE | Al Wafaa Group”.
Canonical URL set
The canonical URL is https://www.alwafaagroup.com/.
Structured data in place
Structured data found: BreadcrumbList, FAQPage, LocalBusiness, Organization and ProfessionalService.
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://www.alwafaagroup.com/sitemap.xml.
AI search readiness
4 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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,075 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.alwafaagroup.com/llms.txt (4 KiB, 0 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.alwafaagroup.com/ai-mobile-app-development declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages without an H1
https://www.alwafaagroup.com/custom-ai-software and https://www.alwafaagroup.com/ai-mobile-app-development have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 37 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
4 small tap targets
4 of 18 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 1,445 words of copy
The homepage carries about 1,445 words of visible text.
8 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Talk to an Expert” and “Call: +971505684147”.
18 calls to action
The homepage has 18 calls to action, for example “Contact”, “Get a Free Consultation” and “Talk to an Expert”.
Social proof on the page
Social proof on the homepage: a star rating and “Trusted by 5,000+ clients”.
Analytics in place
Analytics detected: Google Analytics and Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 4 phone links and 2 email links.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads 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.
1 cookie set on arrival
1Opening 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.
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 alwafaagroup.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Next.js
- Analytics
- Google Analytics
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 21 issues on alwafaagroup.com, including 11 speed issues and 1 SEO issue. 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.