gourmandise.com.tn website review

10 images could be 715 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.1 s faster on a phone.

8 files are served with short cache lifetimes, so returning visitors download them again (278 KiB).

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

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

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

Your mobile performance score is 64. Pages that score under 90 lose visitors before the first paint.

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

4 third-party services load with your homepage (Facebook, Google Tag Manager and Google Maps and others), adding 495 KiB and 380 ms of main-thread time.

Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

3 KiB could be saved by minifying CSS.

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.

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Main Slider”.

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 855 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

Your homepage downloads 2.5 MB in 34 requests on a phone: images 1.4 MB (17), scripts 753 KiB (5) and stylesheets 155 KiB (5). Under 2 MB keeps phones on slow connections fast.

Carte cadeau 557x202_20260319133811.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

6 images (579 KiB) 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.

3 images are downloaded at several times the size a phone draws them, for example WhatsApp-Image-2025-11-25-at-16.46.jpg at 1,253 px wide, shown at 390 px. Resized copies would save about 163 KiB.

1 image further down the page (125 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

1 button has no accessible name, so screen readers announce just “button”.

2 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings should not be empty: 5 elements on the page fail this check, rated minor by axe-core.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization, WebPage and WebSite) but with 2 problems, for example “WebSite: missing name”.

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

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

The homepage links to 44 pages on gourmandise.com.tn and 0 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.

/33-glaces 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.

/ and /33-glaces all use the title “Pâtisserie Tunisienne & Pâtisserie Européenne - Gourmandise”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/module/tvcmsproductcompare/productcomparelist, /cadeaux-coffrets-patisseries-tunisiennes/704-carte-cadeau-50-dt.html, /cadeaux-coffrets-patisseries-tunisiennes/703-carte-cadeau-100-dt.html, /44-coffrets-chocolats and /46-coffrets-patisseries-tunisiennes have no meta description, so Google writes the search snippet from whatever text it finds.

/22-patisserie-fine-tunisie and /27-patisserie-fine-tunisienne use the same meta description. A description written for each page earns more clicks.

/module/tvcmsproductcompare/productcomparelist, /37-traiteur-sale-fin-tunisie, /43-cadeaux-coffrets-patisseries-tunisiennes, /22-patisserie-fine-tunisie, /23-patisserie-europeenne-tunisie and /27-patisserie-fine-tunisienne and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

/module/tvcmsproductcompare/productcomparelist has 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.

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

1 image failed to load on a phone, for example https://gourmandise.com.tn/themes/v1_juicyfruitjams_309/assets/img/themevolty/cupcake.gif.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

gourmandise.com.tn 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.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 41 words of visible text; thin pages give Google and first-time buyers little to go on.

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

gourmandise.com.tn has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 Analytics, Google Tag Manager 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 5 cookies (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 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.