shafitexcel.com website review

29 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.3 s.

About 526 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.5 s faster on a phone.

About 793 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).

A phone's processor spends 4.3 s on main-thread work while loading, 803 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

18 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

6 third-party services load with your homepage (Google Tag Manager, Google Maps and Other Google APIs/SDKs and others), adding 1.1 MB and 690 ms of main-thread time.

The HTML itself could arrive about 550 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 572 ms on a phone.

Google Tag Manager costs a phone 300 ms of main-thread work and 451 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 Maps costs a phone 259 ms of main-thread work and 474 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.

Your server takes 672 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

8 long tasks block the main thread while loading, the longest for 144 ms. During a long task the page ignores taps.

2 files are served with short cache lifetimes, so returning visitors download them again (14 KiB).

8 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Visually, the page fills in at 19.7 s (Speed Index). Good is under 3.4 s.

The first text or image appears after 6.9 s on a phone. Good is under 1.8 s.

Your largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR PRODUCTS”. Most of its time is element render delay (9.2 s).

The page becomes fully interactive after 20.0 s. Good is under 3.8 s.

19 images have no width and height attributes, so the layout jumps as each one loads.

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 115 ms to 136 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.8 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.

3 images weigh 6.4 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 5.6 MB in 133 requests on a phone: images 3.2 MB (39), scripts 1.5 MB (51) and stylesheets 661 KiB (31). Under 2 MB keeps phones on slow connections fast.

6 images (6.7 MB) 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.

3 images are downloaded at several times the size a phone draws them, for example home-prd-yarn-dyed-x.jpg at 1,600 px wide, shown at 433 px. Resized copies would save about 84 KiB.

4 images further down the page (86 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.59 g of CO₂e: 191.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 tap targets are too small or too close together to hit reliably with a finger.

3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

ARIA commands must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

5 images have no alt text, which hurts accessibility and image search.

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.

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 on the page fails this check, rated moderate by axe-core.

11 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 37 pages on shafitexcel.com and 7 external pages.

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.

There is no https://www.shafitexcel.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.

https://www.shafitexcel.com/expo-protection-paris-fair-2026, https://www.shafitexcel.com/cairo-fashion-tex-fair-2026, https://www.shafitexcel.com/munich-fabric-start-2026, https://www.shafitexcel.com/about-us, https://www.shafitexcel.com/yarn-dyed-fabric and https://www.shafitexcel.com/piece-dyed-fabric and 6 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.shafitexcel.com/expo-protection-paris-fair-2026, https://www.shafitexcel.com/cairo-fashion-tex-fair-2026, https://www.shafitexcel.com/munich-fabric-start-2026, https://www.shafitexcel.com/yarn-dyed-fabric, https://www.shafitexcel.com/piece-dyed-fabric and https://www.shafitexcel.com/greige-fabric and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.shafitexcel.com/expo-protection-paris-fair-2026, https://www.shafitexcel.com/cairo-fashion-tex-fair-2026, https://www.shafitexcel.com/munich-fabric-start-2026 and https://www.shafitexcel.com/careers have 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.

https://www.shafitexcel.com/munich-fabric-start-2026 and https://www.shafitexcel.com/about-us took over 3 s to send their HTML from our server.

We fetched 12 pages linked from your homepage and read each the way a search engine does.

5 of 22 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Uncaught Error: pa”.

6 images are served at too low a resolution for sharp phone screens.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 220 words of visible text; thin pages give Google and first-time buyers little to go on.

The homepage shows no opening hours. If customers visit or call, show when.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

Before a visitor clicks anything, the page loads 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.

Opening the homepage sets 3 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.