Website review, no card needed
gourmetegypt.com website review
Visit site (opens in a new tab)Reviewed 4 November 202650 issues · 94 checks
This review found 50 issues worth fixing on gourmetegypt.com, 21 of them high impact, across 94 checks. The most urgent: render-blocking requests. 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
58F- #121,890 of 124,112 reviewed websitesbeats 1%
- #69,418 of 69,786 online storesbeats 0%
- #681 of 725 Magento storesbeats 4%
Closest competitors among Magento stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 4.3 s |
| May 23, 2026 | 4.3 s |
| May 30, 2026 | 4.3 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.7 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 4.9 s |
| Jul 25, 2026 | 4.9 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 4.9 s |
| Aug 22, 2026 | 4.9 s |
| Aug 29, 2026 | 4.8 s |
| Sep 5, 2026 | 4.8 s |
| Sep 12, 2026 | 4.8 s |
| Sep 19, 2026 | 4.8 s |
| Sep 26, 2026 | 4.8 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.8 s |
| Oct 17, 2026 | 4.8 s |
| Oct 24, 2026 | 4.8 s |
| Oct 31, 2026 | 4.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 181 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 195 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 207 ms |
| Jun 20, 2026 | 207 ms |
| Jun 27, 2026 | 207 ms |
| Jul 4, 2026 | 208 ms |
| Jul 11, 2026 | 208 ms |
| Jul 18, 2026 | 210 ms |
| Jul 25, 2026 | 210 ms |
| Aug 1, 2026 | 211 ms |
| Aug 8, 2026 | 219 ms |
| Aug 15, 2026 | 224 ms |
| Aug 22, 2026 | 226 ms |
| Aug 29, 2026 | 225 ms |
| Sep 5, 2026 | 220 ms |
| Sep 12, 2026 | 221 ms |
| Sep 19, 2026 | 221 ms |
| Sep 26, 2026 | 224 ms |
| Oct 3, 2026 | 227 ms |
| Oct 10, 2026 | 226 ms |
| Oct 17, 2026 | 228 ms |
| Oct 24, 2026 | 227 ms |
| Oct 31, 2026 | 227 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.8 s
1.7 s
2.5 s
3.3 s
4.1 s
5.0 s
5.8 s
6.6 s
Speed
Render-blocking requests
2.4 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.4 s.
Reduce unused CSS
1.8 s · 317 KiBAbout 317 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
5,760 HTML elements
The page has 5,760 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Main-thread work: 5.0 s
A phone's processor spends 5.0 s on main-thread work while loading, 3.0 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
600 ms · 189 KiBAbout 189 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and TikTok and others), adding 686 KiB and 581 ms of main-thread time.
Use efficient cache lifetimes
219 KiB5 files are served with short cache lifetimes, so returning visitors download them again (219 KiB).
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 153 ms. During a long task the page ignores taps.
Improve image delivery
121 KiB6 images could be 121 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
32 KiBPolyfills for old browsers add 32 KiB JavaScript that modern phones do not need.
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: 37 ms
37 msYour server sent the HTML in 37 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: 5.1 s
5.1 sReal visitors wait 5.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.30
0.30For real visitors the layout shifts by 0.30 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 15.4 s
15.4 sYour largest element takes 15.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “IVORY Cash back - MobileView”.
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
Speed Index: 10.9 s
10.9 sVisually, the page fills in at 10.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.1 s
4.1 sThe first text or image appears after 4.1 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.289
0.289The layout shifts by 0.289 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 281 ms
281 msReal visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 24% slower for real visitors
+24%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 181 ms to 227 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 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.
Total Blocking Time: 513 ms
513 msScripts block taps and scrolling for 513 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 4.3 s to 4.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 3.1 MB in 485 requests
3.1 MBYour homepage downloads 3.1 MB in 485 requests on a phone: scripts 1.3 MB (359), images 1.0 MB (49) and stylesheets 344 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.89 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.89 g of CO₂e: 107.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 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.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
67 form fields without a label
67 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (25 elements)
Alternative text of images should not be repeated as text: 25 elements on the page fail this check, rated minor by axe-core.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 10 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (279 characters)
Your meta description is 279 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, 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.
943 internal links, 0 external
The homepage links to 943 pages on gourmetegypt.com and 0 external pages.
4 checks passed
Title: 59 characters
Your title is a healthy 59 characters: “Gourmet Egypt | Online Grocery Shopping & Same Day Delivery”.
Structured data in place
Structured data found: Organization and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://gourmetegypt.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://gourmetegypt.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.
3 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,924 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
/, https://gourmetegypt.com/wishlist, https://gourmetegypt.com/sales/order/history, https://gourmetegypt.com/stores/store/redirect/___store/gourmet_egypt_arabic/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VybWV0X2VneXB0X2FyYWJpYw~~, https://gourmetegypt.com/stores/store/redirect/___store/gouna/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VuYQ~~ and https://gourmetegypt.com/stores/store/redirect/___store/northcoast/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1ub3J0aGNvYXN0 all use the title “Gourmet Egypt | Online Grocery Shopping & Same Day Delivery”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages share a meta description
https://gourmetegypt.com/wishlist, https://gourmetegypt.com/sales/order/history, https://gourmetegypt.com/loyalty/rewards, https://gourmetegypt.com/stores/store/redirect/___store/gourmet_egypt_arabic/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VybWV0X2VneXB0X2FyYWJpYw~~, https://gourmetegypt.com/stores/store/redirect/___store/gouna/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VuYQ~~ and https://gourmetegypt.com/stores/store/redirect/___store/northcoast/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1ub3J0aGNvYXN0 use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://gourmetegypt.com/wishlist, https://gourmetegypt.com/sales/order/history, https://gourmetegypt.com/stores/store/redirect/___store/gourmet_egypt_arabic/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VybWV0X2VneXB0X2FyYWJpYw~~, https://gourmetegypt.com/stores/store/redirect/___store/gouna/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1nb3VuYQ~~ and https://gourmetegypt.com/stores/store/redirect/___store/northcoast/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1ub3J0aGNvYXN0 have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages slow to respond
https://gourmetegypt.com/stores/store/redirect/___store/northcoast/___from_store/gourmet_egypt_english/uenc/aHR0cHM6Ly9nb3VybWV0ZWd5cHQuY29tLz9fX19zdG9yZT1ub3J0aGNvYXN0 and https://gourmetegypt.com/sweet-slim-hot-chocolate-sugar-free took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 195 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.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
10 broken images
10 images failed to load on a phone, for example https://gourmetegypt.com/.
55 small tap targets
55 of 140 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 “Cannot read properties of undefined (reading 'customer_email')”.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
A 13-field form
Your longest form asks for 13 fields (4 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 418 words of copy
The homepage carries about 418 words of visible text.
4 checks passed
10 calls to action
The homepage has 10 calls to action, for example “Login / Sign Up”, “Apply” and “Shop”.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Meta Pixel and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, 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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
18 other companies contacted
Loading the homepage contacts 18 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 gourmetegypt.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Fastly
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on gourmetegypt.com, including 21 speed issues, 4 SEO issues and 4 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.