zedbee.in website review

116 files are served with short cache lifetimes, so returning visitors download them again (9.9 MB).

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

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

About 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 68 (desktop: 88). Pages that score under 90 lose visitors before the first paint.

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

The page has 1,897 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

About 116 KiB of JavaScript is downloaded but never used on this page.

1 image could be 18 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 50 ms faster on a phone.

1 third-party service load with your homepage (Google Fonts), adding 153 KiB and 0 ms of main-thread time.

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.

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.

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

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

Your largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Smart HVAC Control & Energy Management for Commercial Build…”. Most of its time is element render delay (2.7 s).

Real visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.1 s (75th percentile). Good is under 1.8 s.

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

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

Your homepage downloads 10.1 MB in 129 requests on a phone: media 7.2 MB (1), images 1.3 MB (18) and fonts 899 KiB (17). Under 2 MB keeps phones on slow connections fast.

1 image further down the page (20 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 2.86 g of CO₂e: 342.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 button has no accessible name, so screen readers announce just “button”.

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.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

6 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.

ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor by axe-core.

Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.

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

The homepage links to 116 pages on zedbee.in and 1 external page.

Your Organization JSON-LD is missing 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.

There is no https://zedbee.in/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.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://zedbee.in/industriies/it-parks-large-campuses, whose canonical is https://zedbee.in/it-parks-large-campuses. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://zedbee.in/our-products, https://zedbee.in/contact-us and https://zedbee.in/portfolio/managing-corporate-change have no <h1> headline, so visitors and search engines get no clear main topic.

https://zedbee.in/industriies/hospitals-healthcare, https://zedbee.in/industriies/retail-malls, https://zedbee.in/industriies/education-institutions, https://zedbee.in/company and https://zedbee.in/career took over 3 s to send their HTML from our server.

We fetched 15 pages linked from your homepage (of 32 found) and read each the way a search engine does.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

1 image is served at too low a resolution for sharp phone screens.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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,116 words of visible text.

Opening the homepage sets 1 cookie (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 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.