Website review, no card needed

alrawabidairy.com logo

alrawabidairy.com website review

Visit site (opens in a new tab)Reviewed 28 October 202654 issues · 93 checks

This review found 54 issues worth fixing on alrawabidairy.com, 27 of them high impact, across 93 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.6 s2.2 sMay 9Oct 242.7 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20263.4 s
May 16, 20263.1 s
May 23, 20262.7 s
May 30, 20262.5 s
Jun 6, 20262.5 s
Jun 13, 20262.5 s
Jun 20, 20262.5 s
Jun 27, 20262.5 s
Jul 4, 20262.4 s
Jul 11, 20262.4 s
Jul 18, 20262.3 s
Jul 25, 20262.3 s
Aug 1, 20262.4 s
Aug 8, 20262.5 s
Aug 15, 20262.5 s
Aug 22, 20262.5 s
Aug 29, 20262.5 s
Sep 5, 20262.5 s
Sep 12, 20262.5 s
Sep 19, 20262.6 s
Sep 26, 20262.7 s
Oct 3, 20262.7 s
Oct 10, 20262.7 s
Oct 17, 20262.8 s
Oct 24, 20262.7 s
Real-visitor tap response (INP)75th percentile, phones
99 ms84 msMay 9Oct 2497 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202694 ms
May 16, 202693 ms
May 23, 202689 ms
May 30, 202688 ms
Jun 6, 202689 ms
Jun 13, 202691 ms
Jun 20, 202692 ms
Jun 27, 202693 ms
Jul 4, 202691 ms
Jul 11, 202690 ms
Jul 18, 202687 ms
Jul 25, 202686 ms
Aug 1, 202689 ms
Aug 8, 202691 ms
Aug 15, 202693 ms
Aug 22, 202694 ms
Aug 29, 202694 ms
Sep 5, 202693 ms
Sep 12, 202691 ms
Sep 19, 202691 ms
Sep 26, 202688 ms
Oct 3, 202691 ms
Oct 10, 202694 ms
Oct 17, 202695 ms
Oct 24, 202697 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 alrawabidairy.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alrawabidairy.com at 0.6 s0.6 s
  2. alrawabidairy.com at 1.1 s1.1 s
  3. alrawabidairy.com at 1.7 s1.7 s
  4. alrawabidairy.com at 2.2 s2.2 s
  5. alrawabidairy.com at 2.8 s2.8 s
  6. alrawabidairy.com at 3.3 s3.3 s
  7. alrawabidairy.com at 3.9 s3.9 s
  8. alrawabidairy.com at 4.4 s4.4 s

Speed

9 to fix46
  • Improve image delivery

    9.4 s · 9.3 MB

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

  • Reduce unused JavaScript

    3.5 s · 325 KiB

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

  • Render-blocking requests

    3.8 s

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

  • Mobile performance score: 46

    46/100

    Your mobile performance score is 46 (desktop: 73). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Reduce unused CSS

    900 ms · 117 KiB

    About 117 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 1,005 KiB and 675 ms of main-thread time.

  • Google CDN adds 610 ms

    610 ms

    Google CDN costs a phone 610 ms of main-thread work and 734 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.8 s

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

  • 9 long tasks on the main thread

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

  • Font display

    200 ms

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

  • Minify JavaScript

    150 ms · 7 KiB

    7 KiB could be saved by minifying JavaScript.

  • Minify CSS

    150 ms · 6 KiB

    6 KiB could be saved by minifying CSS.

  • Phones get a much slower page than desktops

    Desktop scores 73 but mobile only 46. 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: 3 ms

    3 ms

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

Core Web Vitals

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

  • Real-user FCP: 3.0 s

    3.0 s

    Real visitors see the first content after 3.0 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.1 s

    11.1 s

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

  • Largest Contentful Paint: 26.3 s

    26.3 s

    Your largest element takes 26.3 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.3 s

    26.3 s

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

  • Speed Index: 11.1 s

    11.1 s

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

  • Total Blocking Time: 391 ms

    391 ms

    Scripts block taps and scrolling for 391 ms in total while the page loads. Good is under 200 ms.

  • 17 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

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

4 checks passed
  • Real-user INP: 141 ms

    141 ms

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

  • Real-user CLS: 0.00

    0.00

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

  • Largest content (LCP) got 16% faster for real visitors

    -16%

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix18
  • Page weight: 14.5 MB in 84 requests

    14.5 MB

    Your homepage downloads 14.5 MB in 84 requests on a phone: images 12.7 MB (35), scripts 850 KiB (18) and fonts 466 KiB (10). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 3.9 MB together. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.2 MB

    5 images are downloaded at several times the size a phone draws them, for example OY_7024.jpg at 1,800 px wide, shown at 350 px. Resized copies would save about 1.2 MB.

  • 13 images in older formats

    13 images (5.8 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.

  • 12 images below the first screen load straight away

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

  • About 4.1 g of CO₂ per visit

    4.12 g

    By the Sustainable Web Design model, a visit to your homepage emits about 4.12 g of CO₂e: 494.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

15 to fixGoogle 6979
  • Invalid ARIA attributes

    2 elements use ARIA attributes their role does not allow, which confuses screen readers.

  • Certain ARIA roles must contain particular children (2 elements)

    Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.

  • ARIA attributes must conform to valid values (2 elements)

    ARIA attributes must conform to valid values: 2 elements on the page fail this check, rated critical by axe-core.

  • 12 text elements with low contrast

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

  • Hidden but focusable

    6 elements hidden from screen readers can still receive keyboard focus.

  • ARIA input fields must have an accessible name (3 elements)

    ARIA input fields must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (3 elements)

    Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

  • ARIA toggle fields must have an accessible name (1 element)

    ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

  • 1 image without alt text

    1 image has no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (20 elements)

    All page content should be contained by landmarks: 20 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.

  • 8 links without text

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

  • 7 form fields without a label

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

  • Elements marked as presentational should be consistently ignored (2 elements)

    Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

5 to fixGoogle 9271
  • No meta description

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

  • Title is short (9 characters)

    Your title is only 9 characters: “Al Rawabi”. 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.

  • 3 H1 headlines

    There are 3 <h1> headlines (“Freshness You Can Taste”, “Freshness You Can Taste” and “Freshness You Can Taste”). One clear main headline is easier for people and search engines.

  • 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 X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 48 internal links, 11 external

    The homepage links to 48 pages on alrawabidairy.com and 11 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://alrawabidairy.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://alrawabidairy.com/wp-sitemap.xml.

AI search readiness

1 to fix88
  • 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://alrawabidairy.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.

  • Text is in the HTML

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

Other pages

3 to fix85
  • 15 pages without a meta description

    https://alrawabidairy.com/about-us, https://alrawabidairy.com/our-story, https://alrawabidairy.com/our-team, https://alrawabidairy.com/our-products, https://alrawabidairy.com/environment-sustainable and https://alrawabidairy.com/products/lemon-ginger and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://alrawabidairy.com/al-rawabi, whose canonical is https://alrawabidairy.com/tips-and-recipes/al-rawabi-greek-yogurt-pancakes. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 2 pages without an H1

    https://alrawabidairy.com/our-team and https://alrawabidairy.com/our-products have no <h1> headline, so visitors and search engines get no clear main topic.

  • 4 pages with very little text

    https://alrawabidairy.com/our-team, https://alrawabidairy.com/products/lemon-ginger, https://alrawabidairy.com/butcherz and https://alrawabidairy.com/bakerz 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 (of 23 found) and read each the way a search engine does.

4 checks passed
  • Linked pages load

    All 15 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 15 pages that loaded have a <title>.

Best practices

3 to fixGoogle 9285
  • 9 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://alrawabidairy.com/wp-content/themes/alrawabi/assets/css/brand_detail.css?ver=1' be…”.

  • 6 distorted images

    6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

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

  • 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 469 words of copy

    The homepage carries about 469 words of visible text.

3 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact Us”.

  • 2 short forms

    2 short forms (6 fields at most) are right on the homepage, asking for an email.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 1 email link.

Privacy and tracking

  • 1 cookie set on arrival

    1

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

  • 5 other companies contacted

    Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 alrawabidairy.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
Hosting
Cloudflare

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 alrawabidairy.com, including 19 speed issues, 5 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

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