Website review, no card needed

deemah.com logo

deemah.com website review

Visit site (opens in a new tab)Reviewed 30 October 202642 issues · 83 checks

This review found 42 issues worth fixing on deemah.com, 18 of them high impact, across 83 checks. The most urgent: render-blocking requests. 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
4.4 s3.4 sMay 9Oct 244.0 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20264.3 s
May 16, 20264.3 s
May 23, 20264.2 s
May 30, 20264.1 s
Jun 6, 20264.0 s
Jun 13, 20263.9 s
Jun 20, 20263.8 s
Jun 27, 20263.7 s
Jul 4, 20263.8 s
Jul 11, 20263.9 s
Jul 18, 20264.0 s
Jul 25, 20264.1 s
Aug 1, 20264.1 s
Aug 8, 20264.2 s
Aug 15, 20264.2 s
Aug 22, 20264.2 s
Aug 29, 20264.1 s
Sep 5, 20263.9 s
Sep 12, 20263.6 s
Sep 19, 20263.5 s
Sep 26, 20263.5 s
Oct 3, 20263.6 s
Oct 10, 20263.7 s
Oct 17, 20263.9 s
Oct 24, 20264.0 s
Real-visitor tap response (INP)75th percentile, phones
129 ms110 msMay 9Oct 24121 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026112 ms
May 16, 2026112 ms
May 23, 2026113 ms
May 30, 2026113 ms
Jun 6, 2026114 ms
Jun 13, 2026116 ms
Jun 20, 2026112 ms
Jun 27, 2026112 ms
Jul 4, 2026113 ms
Jul 11, 2026113 ms
Jul 18, 2026120 ms
Jul 25, 2026123 ms
Aug 1, 2026126 ms
Aug 8, 2026127 ms
Aug 15, 2026124 ms
Aug 22, 2026123 ms
Aug 29, 2026121 ms
Sep 5, 2026117 ms
Sep 12, 2026119 ms
Sep 19, 2026114 ms
Sep 26, 2026114 ms
Oct 3, 2026114 ms
Oct 10, 2026113 ms
Oct 17, 2026121 ms
Oct 24, 2026121 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 deemah.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. deemah.com at 0.4 s0.4 s
  2. deemah.com at 0.8 s0.8 s
  3. deemah.com at 1.3 s1.3 s
  4. deemah.com at 1.7 s1.7 s
  5. deemah.com at 2.1 s2.1 s
  6. deemah.com at 2.5 s2.5 s
  7. deemah.com at 2.9 s2.9 s
  8. deemah.com at 3.4 s3.4 s

Speed

6 to fix62
  • Render-blocking requests

    1.8 s

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

  • Improve image delivery

    350 ms · 2.8 MB

    15 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused JavaScript

    960 ms · 179 KiB

    About 179 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 960 ms faster on a phone.

  • Mobile performance score: 62

    62/100

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

  • Reduce unused CSS

    660 ms · 124 KiB

    About 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 660 ms faster on a phone.

  • Legacy JavaScript

    350 ms · 8 KiB

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Analytics), adding 209 KiB and 144 ms of main-thread time.

  • 5 long tasks on the main thread

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

  • Font display

    50 ms

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

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

  • Use efficient cache lifetimes

    2 KiB

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

2 checks passed
  • Main-thread work: 1.2 s

    A phone's processor spends 1.2 s on main-thread work while loading, 438 ms of it running JavaScript. That is comfortably low.

  • Server response: 28 ms

    28 ms

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

Core Web Vitals

9 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.7 s

    3.7 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Largest Contentful Paint: 15.0 s

    15.0 s

    Your largest element takes 15.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Indulge In Irresistible Taste: Experience The Traditional F…”.

  • Speed Index: 11.8 s

    11.8 s

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

  • Time to Interactive: 15.7 s

    15.7 s

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 19 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +8%

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

  • Largest content (LCP) held steady for real visitors

    -7%

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

4 checks passed
  • Real-user INP: 129 ms

    129 ms

    Real visitors wait 129 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.

  • Total Blocking Time: 68 ms

    68 ms

    Scripts block the page for only 68 ms while loading. Good is under 200 ms.

  • 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: 4.1 MB in 57 requests

    4.1 MB

    Your homepage downloads 4.1 MB in 57 requests on a phone: images 3.0 MB (28), scripts 453 KiB (16) and fonts 433 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 7 images far larger than shown

    1.7 MB

    7 images are downloaded at several times the size a phone draws them, for example DEEMAH-BLISS-BANNER-EN-scaled.jpg at 2,560 px wide, shown at 392 px. Resized copies would save about 1.7 MB.

  • 2 images over 500 KB

    2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.

  • 17 images in older formats

    17 images (3.4 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.

  • 9 images below the first screen load straight away

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

  • About 1.1 g of CO₂ per visit

    1.15 g

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

Accessibility

7 to fixGoogle 8591
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 9 text elements with low contrast

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

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

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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.

  • 13 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 38 images in the HTML carry an alt attribute.

  • 40 automated accessibility rules passed

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

SEO

4 to fixGoogle 8571
  • 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.

  • Title is short (13 characters)

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

  • 10 links crawlers can't follow

    10 links have no real href, so search engines can't follow them.

  • 37 internal links, 7 external

    The homepage links to 37 pages on deemah.com and 7 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://deemah.com/.

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • 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://deemah.com/sitemap_index.xml.

AI search readiness

1 to fix83
  • Organization data is thin (3 of 6 facts)

    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.

  • No llms.txt

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

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

Other pages

3 to fix80
  • 1 page points its canonical at the homepage

    https://deemah.com/ar 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.

  • 14 pages without a meta description

    https://deemah.com/our-story, https://deemah.com/our-international-presence, https://deemah.com/products, https://deemah.com/videos, https://deemah.com/news and https://deemah.com/contact-us and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages without an H1

    https://deemah.com/videos, https://deemah.com/join-us, https://deemah.com/ar, https://deemah.com/products/biscuits, https://deemah.com/products/cakes and https://deemah.com/products/snacks and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 7 pages with very little text

    https://deemah.com/products, https://deemah.com/videos, https://deemah.com/join-us, https://deemah.com/ar, https://deemah.com/products/cakes and https://deemah.com/products/nuts and 1 other 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.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • Linked pages load

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

Best practices

2 to fixGoogle 9687
  • 20 small tap targets

    20 of 25 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 “Failed to load resource: the server responded with a status of 429 ()”.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix50
  • 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 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 141 words

    The homepage has only about 141 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.

2 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us” and “Join Us”.

  • Analytics in place

    Analytics detected: Google Analytics.

Privacy and tracking

1 to fix
  • 2 trackers load before any consent

    2

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

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 3 other companies contacted

    Loading the homepage contacts 3 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 deemah.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics
Hosting
WordPress.com

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on deemah.com, including 15 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

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