Website review, no card needed

sprinkles.ae logo

sprinkles.ae website review

Visit site (opens in a new tab)Reviewed 20 November 202630 issues · 60 checks

This review found 30 issues worth fixing on sprinkles.ae, 14 of them high impact, across 60 checks. The most urgent: use efficient cache lifetimes. 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

Full-page screenshot of sprinkles.ae (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sprinkles.ae at 0.4 s0.4 s
  2. sprinkles.ae at 0.8 s0.8 s
  3. sprinkles.ae at 1.1 s1.1 s
  4. sprinkles.ae at 1.5 s1.5 s
  5. sprinkles.ae at 1.9 s1.9 s
  6. sprinkles.ae at 2.3 s2.3 s
  7. sprinkles.ae at 2.7 s2.7 s
  8. sprinkles.ae at 3.1 s3.1 s

Speed

10 to fix33
  • Use efficient cache lifetimes

    19.4 s · 5.0 MB

    114 files are served with short cache lifetimes, so returning visitors download them again (5.0 MB).

  • Render-blocking requests

    9.1 s

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

  • Reduce unused CSS

    6.5 s · 1.1 MB

    About 1.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.5 s faster on a phone.

  • Improve image delivery

    5.7 s · 1.4 MB

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

  • Reduce unused JavaScript

    2.1 s · 754 KiB

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

  • Mobile performance score: 33

    33/100

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (chatra.io, Google Tag Manager and Google Fonts and others), adding 668 KiB and 689 ms of main-thread time.

  • chatra.io adds 486 ms

    486 ms

    chatra.io costs a phone 486 ms of main-thread work and 309 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.

  • Minify CSS

    310 ms · 46 KiB

    46 KiB could be saved by minifying CSS.

  • Main-thread work: 2.3 s

    A phone's processor spends 2.3 s on main-thread work while loading, 941 ms 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 208 ms. During a long task the page ignores taps.

  • Font display

    100 ms

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

  • Minify JavaScript

    62 KiB

    62 KiB could be saved by minifying JavaScript.

  • Legacy JavaScript

    26 KiB

    Polyfills for old browsers add 26 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: 234 ms

    234 ms

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

Core Web Vitals

7 to fix39
  • First Contentful Paint: 10.5 s

    10.5 s

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

  • Largest Contentful Paint: 26.6 s

    26.6 s

    Your largest element takes 26.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Best Sellers NAIL CAKEPOPS FROM 240.00 AED BUY FOOTBALL 004…”.

  • Time to Interactive: 26.7 s

    26.7 s

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

  • Speed Index: 12.1 s

    12.1 s

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

  • Cumulative Layout Shift: 0.234

    0.234

    The layout shifts by 0.234 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Total Blocking Time: 438 ms

    438 ms

    Scripts block taps and scrolling for 438 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.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

1 to fix33
  • Page weight: 5.7 MB in 149 requests

    5.7 MB

    Your homepage downloads 5.7 MB in 149 requests on a phone: images 2.2 MB (37), scripts 1.4 MB (41) and stylesheets 1.2 MB (34). Under 2 MB keeps phones on slow connections fast.

  • About 1.6 g of CO₂ per visit

    1.61 g

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

Accessibility

5 to fixGoogle 7070
  • 9 images without alt text

    9 images have no alt text, which hurts accessibility and image search.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 44 text elements with low contrast

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

  • Links look like plain text

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

1 checks passed
  • 5 automated accessibility rules passed

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

SEO

3 to fixGoogle 9286
  • Title is long (86 characters)

    Your title is 86 characters, so Google will cut it off around 60: “Sprinkles :: Cake shops in Dubai | Fabulous Cakes | Cake Delivery Dubai | Themed cakes”.

  • No social preview image

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

  • No XML sitemap

    No XML sitemap at https://www.sprinkles.ae/sitemap.rss, so Google discovers your pages only by following links.

  • 104 internal links, 3 external

    The homepage links to 104 pages on sprinkles.ae and 3 external pages.

5 checks passed
  • Meta description: 131 characters

    Your meta description is 131 characters: “Celebrate your special occasions with Fabulous Cakes from Sprinkles Cake shops in Dubai with Themed cakes, Cake deliver…”.

  • One H1 headline

    Your main headline reads: “Fabulous Cakes | Cupcakes | Cake Delivery Dubai | Online Cakes | Icing Cakes”.

  • Canonical URL set

    The canonical URL is https://www.sprinkles.ae/.

  • Structured data in place

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

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

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

    Your Organization JSON-LD is missing logo, 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://www.sprinkles.ae/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

  • Your server turned our page checks away

    15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.

Best practices

Google 96100
2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

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

    The homepage carries about 303 words of visible text.

3 checks passed
  • 11 calls to action

    The homepage has 11 calls to action, for example “Get a custom quote”, “Contact Us” and “Buy”.

  • 3 short forms

    3 short forms (3 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Analytics.

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.

  • 1 other company contacted

    Loading the homepage contacts 1 host 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 sprinkles.ae, 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 © 2018.

Stack

CMS
WordPress
Framework
jQuery
E-commerce
WooCommerce
Analytics
Google Analytics
Hosting
InMotion Hosting, Inc.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 30 issues on sprinkles.ae, including 17 speed issues, 3 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