Website review, no card needed
egic.com.eg website review
Visit site (opens in a new tab)Reviewed 26 October 202622 issues · 79 checks
This review found 22 issues worth fixing on egic.com.eg, 4 of them high impact, across 79 checks. The most urgent: fails Core Web Vitals for real visitors. 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
91AClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 2.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.4 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 143 ms |
| May 16, 2026 | 140 ms |
| May 23, 2026 | 144 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 147 ms |
| Jun 13, 2026 | 149 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 145 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 138 ms |
| Jul 25, 2026 | 134 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 131 ms |
| Aug 15, 2026 | 135 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 135 ms |
| Sep 5, 2026 | 134 ms |
| Sep 12, 2026 | 130 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 121 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 114 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 109 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
300 ms · 116 KiBAbout 116 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.
2 third-party services on the page
2 third-party services load with your homepage (Google Tag Manager and Google Analytics), adding 181 KiB and 174 ms of main-thread time.
Reduce unused CSS
174 KiBAbout 174 KiB of CSS is downloaded but never applied on this page.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 106 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
3 checks passed
Mobile performance score: 92
92/100Your mobile performance score is 92 (desktop: 97). That is in Google's “good” band (90 and up).
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 365 ms of it running JavaScript. That is comfortably low.
Server response: 324 ms
324 msYour server sent the HTML in 324 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 TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Time to Interactive: 6.0 s
6.0 sThe page becomes fully interactive after 6.0 s. Good is under 3.8 s.
Largest Contentful Paint: 3.0 s
3.0 sYour largest element takes 3.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WATER SUPPLY AND DRAINAGE SOLUTIONS As a leading manufactur…”. Most of its time is element render delay (1.9 s).
Speed Index: 4.1 s
4.1 sVisually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.
9 checks passed
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 87 ms
87 msReal visitors wait 87 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.6 s
1.6 sReal visitors see the first content after 1.6 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 22% faster for real visitors
-22%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 143 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 24% faster for real visitors
-24%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 51 ms
51 msScripts block the page for only 51 ms while loading. Good is under 200 ms.
Images and page weight
1 image in older formats
1 image (130 KiB) 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 0.2 g of CO₂ per visit
0.24 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.24 g of CO₂e: 28.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 861 KiB in 49 requests
861 KiBYour homepage downloads 861 KiB in 49 requests on a phone: scripts 401 KiB (33), images 190 KiB (6) and stylesheets 135 KiB (5). That is a lean page.
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
1 text element with low contrast
1 text element doesn'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.
Banner landmark should not be contained in another landmark (1 element)
Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Headings skip levels
Headings skip levels (h1 → h5 and h2 → h6), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 24 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 6 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Home Page | EGIC Egypt - Superior German Quality - Official Website”.
3 H1 headlines
There are 3 <h1> headlines (“WATER SUPPLY AND”, “DRAINAGE SOLUTIONS” and “MADE WITH”). One clear main headline is easier for people and search engines.
131 internal links, 15 external
The homepage links to 131 pages on egic.com.eg and 15 external pages.
6 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “EGIC Egypt - Leading manufacturer of water supply and drainage solutions. Superior German quality products for resident…”.
Canonical URL set
The canonical URL is https://www.egic.com.eg/.
Structured data in place
Structured data found: ImageObject, Organization, Place, ProfessionalService 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://www.egic.com.eg/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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (503 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.egic.com.eg/llms.txt (2 KiB, 16 links), a plain-text guide to the site for AI tools.
Other pages
2 pages share a title
https://www.egic.com.eg/de/startseite and https://www.egic.com.eg/fr/page-daccueil all use the title “EGIC Egyptian German Industrial Corporate | EGIC Egypt”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.egic.com.eg/socialwall has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.egic.com.eg/de/startseite and https://www.egic.com.eg/fr/page-daccueil use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://www.egic.com.eg/products/water-supply-solutions-plumbing-fitting, https://www.egic.com.eg/products/drainage-solutions/kessel-above-the-ground, https://www.egic.com.eg/products/drainage-solutions/smart-home-drainage, https://www.egic.com.eg/careers, https://www.egic.com.eg/socialwall and https://www.egic.com.eg/products/drainage-solutions have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.egic.com.eg/ar/%d8%a7%d9%84%d8%b5%d9%81%d8%ad%d8%a9-%d8%a7%d9%84%d8%b1%d8%a6%d9%8a%d8%b3%d9%8a%d8%a9 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 36 found) and read each the way a search engine does.
4 checks passed
Linked pages load
14 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 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
10 of 11 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 phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 4 trust badges. 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.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 335 words of copy
The homepage carries about 335 words of visible text.
6 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Subscribe” and “Request Inspections”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
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.
3 other companies contacted
Loading the homepage contacts 3 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 egic.com.eg, 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
- 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 22 issues on egic.com.eg, including 6 speed issues, 2 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.