alrifai.com website review

The page goes through 2 redirects before it starts loading, costing about 57.0 s. Link and advertise the final URL directly.

About 3.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 23.2 s faster on a phone.

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

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

The page has 5,292 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

8 third-party services load with your homepage (YouTube, Google Tag Manager and WordPress and others), adding 1.8 MB and 633 ms of main-thread time.

YouTube costs a phone 447 ms of main-thread work and 967 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.

48 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 120 ms of main-thread work and 434 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.

WordPress costs a phone 60 ms of main-thread work and 369 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.

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

22 KiB could be saved by minifying CSS.

About 21 KiB of CSS is downloaded but never applied on this page.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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 visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.

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

Your largest element takes 67.9 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

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

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

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

Your homepage downloads 11.5 MB in 1,312 requests on a phone: scripts 7.1 MB (287), images 1.8 MB (286) and other files 1.3 MB (618). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 3 elements on the page fail this check, rated critical by axe-core.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

1 link inside paragraphs relies on colour alone to stand out.

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

All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Your title is only 20 characters: “Home - Rifai Lebanon”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 4 <h1> headlines (“Local Delivery”, “Click & Collect” and “Customer support”). One clear main headline is easier for people and search engines.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 720 pages on alrifai.com and 10 external pages.

Your Organization JSON-LD is missing 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.

There is no /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.

We fetched 15 pages linked from your homepage (of 102 found) and read each the way a search engine does.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).

6 errors were logged to the browser console while the page loaded, for example “Uncaught TurnstileError: [Cloudflare Turnstile] Error: 400020.”.

Chrome logged issues while loading the page (“Cookie”).

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

1 link go through two or more redirects, for example https://fr.alrifai.com/product-category/nuts-seeds/.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

alrifai.com is registered until Oct 2026. If it lapses, the site and its email stop working and someone else can buy the name. Renew it, and turn on auto-renew.

alrifai.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

alrifai.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,608 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta 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.

Opening the homepage sets 30 cookies, 1 of them by other companies (measured from a US location before any click).

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.

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