Website review, no card needed
alwatania.sa website review
Visit site (opens in a new tab)Reviewed 30 October 202652 issues · 86 checks
This review found 52 issues worth fixing on alwatania.sa, 21 of them high impact, across 86 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
62D- #121,115 of 126,304 reviewed websitesbeats 3%
- #69,242 of 70,423 online storesbeats 1%
- #2,847 of 2,969 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.6 s |
| Jun 6, 2026 | 3.7 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.7 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.9 s |
| Aug 22, 2026 | 3.9 s |
| Aug 29, 2026 | 4.1 s |
| Sep 5, 2026 | 4.0 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.8 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 94 ms |
| May 16, 2026 | 94 ms |
| May 23, 2026 | 94 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 98 ms |
| Jun 13, 2026 | 95 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 100 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 101 ms |
| Jul 25, 2026 | 100 ms |
| Aug 1, 2026 | 102 ms |
| Aug 8, 2026 | 107 ms |
| Aug 15, 2026 | 118 ms |
| Aug 22, 2026 | 129 ms |
| Aug 29, 2026 | 142 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 143 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 148 ms |
| Oct 10, 2026 | 151 ms |
| Oct 17, 2026 | 146 ms |
| Oct 24, 2026 | 150 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
1.7 s
3.3 s
5.0 s
6.7 s
8.4 s
10.0 s
11.7 s
13.4 s
Speed
Use efficient cache lifetimes
1.2 s · 2.6 MB72 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
Reduce unused JavaScript
1.1 s · 710 KiBAbout 710 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
1.4 s23 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 45
45/100Your mobile performance score is 45. 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 (Google CDN, Facebook and Google Tag Manager and others), adding 1.7 MB and 1.4 s of main-thread time.
Improve image delivery
1.4 MB9 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 632 ms
632 msGoogle CDN costs a phone 632 ms of main-thread work and 773 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.
Font display
450 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 450 ms).
Reduce unused CSS
300 ms · 89 KiBAbout 89 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 296 ms
296 msFacebook costs a phone 296 ms of main-thread work and 333 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 Tag Manager adds 260 ms
260 msGoogle Tag Manager costs a phone 260 ms of main-thread work and 356 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 226 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 40 KiBPolyfills for old browsers add 40 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
12 KiB12 KiB could be saved by minifying CSS.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
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.
1 checks passed
Server response: 112 ms
112 msYour server sent the HTML in 112 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.
Real-user LCP: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.89
0.89For real visitors the layout shifts by 0.89 (75th percentile). Good is under 0.1.
Real-user FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Speed Index: 21.6 s
21.6 sVisually, the page fills in at 21.6 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 22.4 s
22.4 sThe page becomes fully interactive after 22.4 s. Good is under 3.8 s.
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load duration (5.9 s).
First Contentful Paint: 3.8 s
3.8 sThe first text or image appears after 3.8 s on a phone. Good is under 1.8 s.
Tap response (INP) got 57% slower for real visitors
+57%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 94 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 561 ms
561 msScripts block taps and scrolling for 561 ms in total while the page loads. Good is under 200 ms.
9 images without width and height
9 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 135 ms
135 msReal visitors wait 135 ms for the page to respond to a tap (75th percentile). 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
Page weight: 4.3 MB in 100 requests
4.3 MBYour homepage downloads 4.3 MB in 100 requests on a phone: images 2.0 MB (24), scripts 1.7 MB (42) and other files 358 KiB (12). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
awp_ordering-online_splash-screen-scaled.jpg weighs 613 KiB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (613 KiB) is 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.
1 image far larger than shown
13 KiB1 image is downloaded at several times the size a phone draws it, for example awp_ordering-online_splash-screen-scaled.jpg at 1,183 px wide, shown at 390 px. Resized copies would save about 13 KiB.
1 image below the first screen load straight away
1 image further down the page (28 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.2 g of CO₂ per visit
1.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.23 g of CO₂e: 147.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
40 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: 40 passed and 7 failed. 4 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.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
35 internal links, 12 external
The homepage links to 35 pages on alwatania.sa and 12 external pages.
5 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “جودة بأيدي أمينة | دواجن الوطنية”.
Canonical URL set
The canonical URL is https://alwatania.sa/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
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://alwatania.sa/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
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.
llms.txt published
The site publishes https://alwatania.sa/llms.txt (23 KiB, 192 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.
Other pages
3 linked pages hidden from search
https://alwatania.sa/recipes/feleh-aldjaj-ma-sslsstt-alzafran, https://alwatania.sa/recipes/djaj-mhshe-balarz and https://alwatania.sa/recipes/btdatds-mhrwstt-baldjaj are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
4 pages share 2 titles
https://alwatania.sa/wssfat and https://alwatania.sa/ar/wssfat all use the title “وصفات | دواجن الوطنية”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://alwatania.sa/product-tag/jmea-almntjat, https://alwatania.sa/wssfat, https://alwatania.sa/ientaj, https://alwatania.sa/tarf-alena, https://alwatania.sa/mjmwatt-mkhrjen and https://alwatania.sa/news and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://alwatania.sa/en and https://alwatania.sa/en/home use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://alwatania.sa/en, whose canonical is https://alwatania.sa/en/home. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
11 pages without an H1
https://alwatania.sa/product-tag/jmea-almntjat, https://alwatania.sa/wssfat, https://alwatania.sa/tarf-alena, https://alwatania.sa/en, https://alwatania.sa/news and https://alwatania.sa/csr-ar and 5 others have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://alwatania.sa/product-tag/jmea-almntjat, https://alwatania.sa/wssfat, https://alwatania.sa/ientaj, https://alwatania.sa/tarf-alena, https://alwatania.sa/mjmwatt-mkhrjen and https://alwatania.sa/news and 4 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.
11 pages slow to respond
https://alwatania.sa/mjmwatt-mkhrjen, https://alwatania.sa/en, https://alwatania.sa/news, https://alwatania.sa/csr-ar, https://alwatania.sa/en/home and https://alwatania.sa/recipes/feleh-aldjaj-ma-sslsstt-alzafran and 5 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 18 found) and read each the way a search engine does.
2 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 11 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 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.
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and TikTok Pixel.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager, Meta Pixel and TikTok Pixel (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.
15 cookies set on arrival
15Opening the homepage sets 15 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.
12 other companies contacted
Loading the homepage contacts 12 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 alwatania.sa, 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
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on alwatania.sa, including 24 speed issues, 3 SEO issues and 5 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.