Website review, no card needed
dicema.com website review
Visit site (opens in a new tab)Reviewed 22 October 202637 issues · 83 checks
This review found 37 issues worth fixing on dicema.com, 19 of them high impact, across 83 checks. The most urgent: improve image delivery. 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
68DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.9 s |
| May 9, 2026 | 5.8 s |
| May 16, 2026 | 5.8 s |
| May 23, 2026 | 6.5 s |
| May 30, 2026 | 7.1 s |
| Jun 6, 2026 | 5.6 s |
| Jun 13, 2026 | 5.5 s |
| Jun 20, 2026 | 2.4 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 4.9 s |
| Jul 11, 2026 | 4.9 s |
| Jul 18, 2026 | 5.9 s |
| Jul 25, 2026 | 5.9 s |
| Aug 1, 2026 | 5.1 s |
| Aug 8, 2026 | 5.9 s |
| Aug 15, 2026 | 5.8 s |
| Aug 22, 2026 | 5.0 s |
| Aug 29, 2026 | 5.6 s |
| Sep 5, 2026 | 4.1 s |
| Sep 12, 2026 | 4.4 s |
| Sep 19, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 175 ms |
| May 9, 2026 | 180 ms |
| May 16, 2026 | 180 ms |
| May 23, 2026 | 186 ms |
| May 30, 2026 | 181 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 178 ms |
| Jul 18, 2026 | 234 ms |
| Jul 25, 2026 | 237 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 187 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
Speed
Improve image delivery
15.3 s · 2.9 MB1 image could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 15.3 s faster on a phone.
Use efficient cache lifetimes
14.8 s · 2.8 MB119 files are served with short cache lifetimes, so returning visitors download them again (2.8 MB).
Reduce unused JavaScript
5.5 s · 749 KiBAbout 749 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.5 s faster on a phone.
Render-blocking requests
1.7 s27 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.7 s.
Font display
1.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.3 s).
Mobile performance score: 32
32/100Your mobile performance score is 32 (desktop: 44). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 1.7 MB and 1.4 s of main-thread time.
Reduce unused CSS
750 ms · 129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
Google Tag Manager adds 592 ms
592 msGoogle Tag Manager costs a phone 592 ms of main-thread work and 560 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.
Google CDN adds 397 ms
397 msGoogle CDN costs a phone 397 ms of main-thread work and 734 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 442 ms. During a long task the page ignores taps.
Facebook adds 254 ms
254 msFacebook costs a phone 254 ms of main-thread work and 225 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.
1,505 HTML elements
The page has 1,505 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 32.5 s
32.5 sYour largest element takes 32.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 33.5 s
33.5 sThe page becomes fully interactive after 33.5 s. Good is under 3.8 s.
Speed Index: 15.2 s
15.2 sVisually, the page fills in at 15.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
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.
22 images without width and height
22 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-17, real Chrome visitors' tap response (inp) went from 175 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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.
2 checks passed
Largest content (LCP) got 20% faster for real visitors
-20%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.9 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.9 MB in 169 requests
5.9 MBYour homepage downloads 5.9 MB in 169 requests on a phone: images 3.2 MB (51), scripts 1.9 MB (53) and other files 375 KiB (26). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
423fbfe1479a6d8a711e2d48e336c1d8cfbf5e49-1.gif weighs 3.0 MB. On a phone connection a single image that size takes seconds.
1 image in older formats
1 image (3.0 MB) is 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.
About 1.7 g of CO₂ per visit
1.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.66 g of CO₂e: 199.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
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.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
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.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
27 form fields without a label
27 form fields have no label, so screen readers announce an empty box and autofill guesses.
9 links without text
9 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 61 images in the HTML carry an alt attribute.
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 2 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.
94 internal links, 6 external
The homepage links to 94 pages on dicema.com and 6 external pages.
7 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “We are passionate to create deeply connected brands, services, and campaigns to enable stable and successful relationsh…”.
Title: 62 characters
Your title is a healthy 62 characters: “🎯 Dice | Strategic Agency For Events & Social In Saudi Arabia”.
Canonical URL set
The canonical URL is https://dicema.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://dicema.com/sitemap_index.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (862 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://dicema.com/llms.txt (6 KiB, 12 links), a plain-text guide to the site for AI tools.
Other pages
5 pages share a meta description
https://dicema.com/about, https://dicema.com/projects, https://dicema.com/spark-ai, https://dicema.com/careers and https://dicema.com/insights use the same meta description. A description written for each page earns more clicks.
3 pages without an H1
https://dicema.com/about, https://dicema.com/projects and https://dicema.com/careers have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 63 found) and read each the way a search engine does.
6 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.
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 15 pages that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 10 tappable elements near the top are at least 24 px.
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
A 13-field form
Your longest form asks for 13 fields (2 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 488 words of copy
The homepage carries about 488 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “START THE CONVERSATION”.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 4 phone links 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 Microsoft Clarity (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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
17 other companies contacted
Loading the homepage contacts 17 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 dicema.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 © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Tag Manager | Microsoft Clarity
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 37 issues on dicema.com, including 20 speed issues, 1 SEO issue 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.