Website review, no card needed
alromaizan.com website review
Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 81 checks
This review found 41 issues worth fixing on alromaizan.com, 16 of them high impact, across 81 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
60DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.0 s |
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.5 s |
| May 30, 2026 | 4.5 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.3 s |
| Jun 20, 2026 | 4.2 s |
| Jun 27, 2026 | 4.2 s |
| Jul 4, 2026 | 4.3 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.5 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 4.8 s |
| Aug 8, 2026 | 4.7 s |
| Aug 15, 2026 | 4.8 s |
| Aug 22, 2026 | 4.8 s |
| Aug 29, 2026 | 5.0 s |
| Sep 5, 2026 | 5.1 s |
| Sep 12, 2026 | 5.1 s |
| Sep 19, 2026 | 5.0 s |
| Sep 26, 2026 | 4.7 s |
| Oct 3, 2026 | 4.6 s |
| Oct 10, 2026 | 4.5 s |
| Oct 17, 2026 | 4.4 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 213 ms |
| May 9, 2026 | 203 ms |
| May 16, 2026 | 201 ms |
| May 23, 2026 | 202 ms |
| May 30, 2026 | 204 ms |
| Jun 6, 2026 | 199 ms |
| Jun 13, 2026 | 196 ms |
| Jun 20, 2026 | 193 ms |
| Jun 27, 2026 | 197 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 198 ms |
| Jul 18, 2026 | 199 ms |
| Jul 25, 2026 | 198 ms |
| Aug 1, 2026 | 198 ms |
| Aug 8, 2026 | 195 ms |
| Aug 15, 2026 | 196 ms |
| Aug 22, 2026 | 191 ms |
| Aug 29, 2026 | 198 ms |
| Sep 5, 2026 | 200 ms |
| Sep 12, 2026 | 200 ms |
| Sep 19, 2026 | 203 ms |
| Sep 26, 2026 | 202 ms |
| Oct 3, 2026 | 202 ms |
| Oct 10, 2026 | 204 ms |
| Oct 17, 2026 | 204 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
2.2 s
4.3 s
6.5 s
8.7 s
10.8 s
13.0 s
15.2 s
17.3 s
Speed
Improve image delivery
2.2 s · 1.3 MB21 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.2 s faster on a phone.
Render-blocking requests
2.5 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Reduce unused JavaScript
1.4 s · 960 KiBAbout 960 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.
Mobile performance score: 26
26/100Your mobile performance score is 26 (desktop: 52). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Google CDN and others), adding 1.7 MB and 1.3 s of main-thread time.
Google Tag Manager adds 656 ms
656 msGoogle Tag Manager costs a phone 656 ms of main-thread work and 881 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.
Main-thread work: 3.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 291 ms. During a long task the page ignores taps.
Google CDN adds 155 ms
155 msGoogle CDN costs a phone 155 ms of main-thread work and 351 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.
Use efficient cache lifetimes
221 KiB4 files are served with short cache lifetimes, so returning visitors download them again (221 KiB).
Reduce unused CSS
77 KiBAbout 77 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 52 but mobile only 26. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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 CLS: 0.49
0.49For real visitors the layout shifts by 0.49 (75th percentile). Good is under 0.1.
Real-user FCP: 3.3 s
3.3 sReal visitors see the first content after 3.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.0 s
2.0 sReal visitors wait 2.0 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 29.2 s
29.2 sThe page becomes fully interactive after 29.2 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 7.5 s
7.5 sYour largest element takes 7.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WATCH AND JEWELLERY MIDDLE EAST SHOW”. Most of its time is resource load delay (4.7 s).
Cumulative Layout Shift: 0.478
0.478The layout shifts by 0.478 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 800 ms
800 msScripts block taps and scrolling for 800 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.9 s
3.9 sReal visitors wait 3.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 213 ms to 204 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.0 s to 4.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 5.7 MB in 250 requests
5.7 MBYour homepage downloads 5.7 MB in 250 requests on a phone: images 2.4 MB (23), scripts 2.2 MB (106) and other files 906 KiB (46). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
q46y6xnld6inzoyplhg1.webp weighs 548 KiB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
q46y6xnld6inzoyplhg1.webp 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).
2 images far larger than shown
151 KiB2 images are downloaded at several times the size a phone draws them, for example falvffgtqhs7ll3rnsrv.webp at 2,048 px wide, shown at 358 px. Resized copies would save about 151 KiB.
About 1.6 g of CO₂ per visit
1.61 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.61 g of CO₂e: 192.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
18 tap targets too small
18 tap targets are too small or too close together to hit reliably with a finger.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 38 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No XML sitemap
No XML sitemap at https://alromaizan.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at alromaizan.com/robots.txt, the first file search crawlers ask for.
14 internal links, 1 external
The homepage links to 14 pages on alromaizan.com and 1 external page.
5 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Shop Gold Jewellery online in the UAE, KSA, QATAR & OMAN. Find our exclusive gold & diamond jewellery collections at Al…”.
One H1 headline
Your main headline reads: “WATCH AND JEWELLERY MIDDLE EAST SHOW”.
Title: 44 characters
Your title is a healthy 44 characters: “Al Romaizan | Online Gold Shop - Al Romaizan”.
Canonical URL set
The canonical URL is https://alromaizan.com/.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://alromaizan.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Other pages
2 pages share a title
https://alromaizan.com/page/watch-jewellery-middle-east-show and https://alromaizan.com/page/emirates-pride-collection all use the title “- Al Romaizan”. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages share a meta description
https://alromaizan.com/product/MJ-NC-MN172-00/18k-ramsha-gold-necklace and https://alromaizan.com/product/MJ-NC-MS161-00/18k-life-gold-necklace use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://alromaizan.com/category/online-exclusives, whose canonical is https://alromaizan.com/online-exclusives. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://alromaizan.com/product/GL-NC-GN652-00/18k-pride-of-the-emirates-1, https://alromaizan.com/product/GL-ST-GS1347-00/18k-pride-of-the-emirates, https://alromaizan.com/product/MJ-NC-MN172-00/18k-ramsha-gold-necklace and https://alromaizan.com/product/MJ-NC-MS161-00/18k-life-gold-necklace have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://alromaizan.com/product/GL-ST-GS1347-00/18k-pride-of-the-emirates took over 3 s to send its HTML from our server.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
4 checks passed
Linked pages load
All 9 pages we checked loaded without an error.
Every page has a meta description
All 9 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 9 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
11 of 13 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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 114 words
The homepage has only about 114 words of visible text; thin pages give Google and first-time buyers little to go on.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 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.
2 other companies contacted
Loading the homepage contacts 2 hosts 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 alromaizan.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on alromaizan.com, including 22 speed issues, 3 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.