Website review, no card needed
alshams.org website review
Visit site (opens in a new tab)Reviewed 3 November 202631 issues · 66 checks
This review found 31 issues worth fixing on alshams.org, 19 of them high impact, across 66 checks. The most urgent: use efficient cache lifetimes. 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
62D- #110,961 of 115,529 reviewed websitesbeats 3%
- #65,429 of 66,525 online storesbeats 1%
- #2,526 of 2,636 WooCommerce storesbeats 3%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jul 18, 2026 | 5.6 s |
| Jul 25, 2026 | 5.5 s |
| Aug 1, 2026 | 6.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 2.4 s |
| Sep 26, 2026 | 2.4 s |
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
Use efficient cache lifetimes
11.3 s · 8.5 MB111 files are served with short cache lifetimes, so returning visitors download them again (8.5 MB).
Improve image delivery
5.9 s · 5.3 MB21 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.9 s faster on a phone.
Render-blocking requests
7.5 s34 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.5 s.
Reduce unused CSS
4.0 s · 785 KiBAbout 785 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.0 s faster on a phone.
Font display
2.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.1 s).
Mobile performance score: 34
34/100Your mobile performance score is 34. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
300 ms · 374 KiBAbout 374 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, lfeeder.com and JSDelivr CDN and others), adding 234 KiB and 170 ms of main-thread time.
Minify CSS
150 ms · 7 KiB7 KiB could be saved by minifying CSS.
Document request latency
89 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 82 ms. During a long task the page ignores taps.
Minify JavaScript
13 KiB13 KiB could be saved by minifying JavaScript.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 277 ms of it running JavaScript. That is comfortably low.
Server response: 543 ms
543 msYour server sent the HTML in 543 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 15.9 s
15.9 sVisually, the page fills in at 15.9 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 14.0 s
14.0 sThe page becomes fully interactive after 14.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.483
0.483The layout shifts by 0.483 while loading, so content jumps under the reader's thumb. Good is under 0.1.
62 images without width and height
62 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.
2 checks passed
Largest content (LCP) got 39% faster for real visitors
-39%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.4 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.1 MB in 120 requests
9.1 MBYour homepage downloads 9.1 MB in 120 requests on a phone: images 6.6 MB (43), stylesheets 888 KiB (31) and scripts 867 KiB (41). Under 2 MB keeps phones on slow connections fast.
About 2.6 g of CO₂ per visit
2.57 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.57 g of CO₂e: 308.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 images without alt text
30 images have no alt text, which hurts accessibility and image search.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Unlabelled dropdowns
1 dropdown has no label.
Hidden but focusable
11 elements hidden from screen readers can still receive keyboard focus.
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
6 links without text
6 links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
41 internal links, 12 external
The homepage links to 41 pages on alshams.org and 12 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Bathroom, Kitchen, Bedroom & Roof Tiles | Alshams”.
Title: 58 characters
Your title is a healthy 58 characters: “Bathroom, Kitchen, Bedroom & Roof Tiles | Alshams AL Shams”.
Canonical URL set
The canonical URL is https://alshams.org/.
Structured data in place
Structured data found: BreadcrumbList, WebPage and WebSite.
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://alshams.org/sitemap_index.xml.
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://alshams.org/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
5 linked pages are broken
Your homepage links to https://alshams.org/product-category/ceramic-tile/floor-tile, https://alshams.org/product-category/ceramic-tile/floor-tile-outdoor, https://alshams.org/product-category/ceramic-tile/wall-tile, https://alshams.org/product-category/ceramic-tile/wall-tile-elevation and https://alshams.org/product-category/ceramic-tile/decorative-panel, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages without a meta description
https://alshams.org/contact-us and https://alshams.org/milestone have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://alshams.org/contact-us and https://alshams.org/milestone have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://alshams.org/contact-us took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 2 pages that loaded have a <title>.
Best practices
2 console errors
2 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 404 (Not Found)”).
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
A 10-field form
Your longest form asks for 10 fields (4 required). Every extra field lowers completion.
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 471 words of copy
The homepage carries about 471 words of visible text.
3 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “ENQUIRE NOW”.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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 alshams.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on alshams.org, including 13 speed issues, 2 SEO issues and 2 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.