byshameel.com website review

Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

8 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

About 251 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.

8 third-party services load with your homepage (website-files.com, Google Tag Manager and cloudfront.net and others), adding 1.8 MB and 395 ms of main-thread time.

website-files.com costs a phone 229 ms of main-thread work and 1.5 MB 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.

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

About 18 KiB of CSS is downloaded but never applied on this page.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying CSS.

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

Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We help fashion brands create winning products. Let’s get s…”.

The layout shifts by 0.464 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

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

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

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.

Your homepage downloads 2.0 MB in 51 requests on a phone: images 1.4 MB (28), scripts 566 KiB (16) and fonts 30 KiB (1). Under 2 MB keeps phones on slow connections fast.

6 images (1.1 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.

1 image further down the page (33 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

4 dropdowns have no label.

All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

9 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

There are 6 <h1> headlines (“We help fashion brands create winning products.”, “Phase 1: Product Discovery” and “Phase 2: Concept Development”). One clear main headline is easier for people and search engines.

Your meta description is 230 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (BreadcrumbList, FAQPage, Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.

The homepage links to 11 pages on byshameel.com and 4 external pages.

There is no https://www.byshameel.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.byshameel.com/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

https://www.byshameel.com/blog 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.

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

Large scripts ship without source maps.

Your longest form asks for 9 fields (9 required). Every extra field lowers completion.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 1,104 words of visible text.

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.