Website review, no card needed
elsewedy-ind.com website review
Visit site (opens in a new tab)Reviewed 26 October 202627 issues · 74 checks
This review found 27 issues worth fixing on elsewedy-ind.com, 11 of them high impact, across 74 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
82B- #32,763 of 115,810 reviewed websitesbeats 66%
- #22,089 of 66,602 online storesbeats 60%
- #392 of 2,639 WooCommerce storesbeats 81%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.4 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.8 s |
| Jul 11, 2026 | 3.8 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 3.8 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 3.8 s |
| Aug 22, 2026 | 3.8 s |
| Aug 29, 2026 | 3.8 s |
| Sep 5, 2026 | 3.8 s |
| Sep 12, 2026 | 3.9 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 195 ms |
| May 16, 2026 | 188 ms |
| May 23, 2026 | 191 ms |
| May 30, 2026 | 186 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 129 ms |
| Jun 27, 2026 | 135 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 149 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 147 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 137 ms |
| Aug 22, 2026 | 139 ms |
| Aug 29, 2026 | 140 ms |
| Sep 5, 2026 | 145 ms |
| Sep 12, 2026 | 149 ms |
| Sep 19, 2026 | 164 ms |
| Sep 26, 2026 | 168 ms |
| Oct 3, 2026 | 172 ms |
| Oct 10, 2026 | 172 ms |
| Oct 17, 2026 | 161 ms |
| Oct 24, 2026 | 168 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
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.4 s
Speed
Improve image delivery
8.6 s · 4.1 MB11 images could be 4.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 8.6 s faster on a phone.
Use efficient cache lifetimes
1.6 s · 980 KiB111 files are served with short cache lifetimes, so returning visitors download them again (980 KiB).
Render-blocking requests
2.5 s33 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 63
63/100Your mobile performance score is 63 (desktop: 71). Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
450 ms · 106 KiBAbout 106 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused JavaScript
450 ms · 99 KiBAbout 99 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 866 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 9 KiB9 KiB could be saved by minifying CSS.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 96 ms. During a long task the page ignores taps.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 140 KiB and 0 ms of main-thread time.
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: 180 ms
180 msYour server sent the HTML in 180 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 21.6 s
21.6 sYour largest element takes 21.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 21.9 s
21.9 sThe page becomes fully interactive after 21.9 s. Good is under 3.8 s.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user INP: 178 ms
178 msReal visitors wait 178 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 14% faster for real visitors
-14%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 195 ms to 168 ms 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).
Total Blocking Time: 50 ms
50 msScripts block the page for only 50 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.6 MB in 125 requests
9.6 MBYour homepage downloads 9.6 MB in 125 requests on a phone: images 8.7 MB (26), scripts 436 KiB (46) and fonts 274 KiB (8). Under 2 MB keeps phones on slow connections fast.
2 images in older formats
2 images (458 KiB) 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.
2 images below the first screen load straight away
2 images further down the page (58 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.7 g of CO₂ per visit
2.72 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.72 g of CO₂e: 326.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
18 images without alt text
18 images have no alt text, which hurts accessibility and image search.
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.
1 checks passed
46 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: 46 passed and 2 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.
Title is short (26 characters)
Your title is only 26 characters: “Home - Elsewedy Industries”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links with vague text
7 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
76 internal links, 25 external
The homepage links to 76 pages on elsewedy-ind.com and 25 external pages.
5 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “El Sewedy Industries Group was established by Mr. Ahmed Sadek El Sewedy in 1938 in Egypt and across the Middle East as …”.
Canonical URL set
The canonical URL is https://elsewedy-ind.com/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
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://elsewedy-ind.com/sitemap_index.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing url, 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://elsewedy-ind.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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (609 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a meta description
https://elsewedy-ind.com/ahmed-sadek has no meta description, so Google writes the search snippet from whatever text it finds.
10 pages share a meta description
https://elsewedy-ind.com/el-sewedy-cement-co-escc, https://elsewedy-ind.com/el-sewedy-company-ready-mix, https://elsewedy-ind.com/el-sewedy-chemical-industries, https://elsewedy-ind.com/terrazzo, https://elsewedy-ind.com/fiber-cement-board-plant and https://elsewedy-ind.com/block-products-plant and 4 others use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://elsewedy-ind.com/about-us, https://elsewedy-ind.com/contactt, https://elsewedy-ind.com/el-sewedy-cement-co-escc, https://elsewedy-ind.com/el-sewedy-company-ready-mix, https://elsewedy-ind.com/el-sewedy-chemical-industries and https://elsewedy-ind.com/terrazzo and 8 others 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 22 found) and read each the way a search engine does.
5 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.
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
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css2?family=cairo:ital,wght@0,300;0,400;0,500;0,600;0,700;1,3…”.
2 checks passed
Tap targets are thumb-sized
10 of 12 tappable elements near the top are at least 24 px.
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.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 348 words of copy
The homepage carries about 348 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US” and “LEARN MORE”.
25 calls to action
The homepage has 25 calls to action, for example “Contact Us” and “Learn more”.
1 short form
A short form (3 fields at most) is right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 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 elsewedy-ind.com, 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
- Hosting
- F5
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 27 issues on elsewedy-ind.com, including 12 speed issues, 4 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.