jibrilsoft.com website review

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

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

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

7 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

1 file is served with short cache lifetimes, so returning visitors download them again (67 KiB).

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

4 third-party services load with your homepage (JSDelivr CDN, cloudfront.net and Shopify and others), adding 190 KiB and 280 ms of main-thread time.

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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.

Your largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

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

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

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

1 image 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.

1 image is downloaded at several times the size a phone draws it, for example Group_1179.png at 1,228 px wide, shown at 360 px. Resized copies would save about 36 KiB.

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

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

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.

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

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

Your title is 95 characters, so Google will cut it off around 60: “Hire dedicated ecommerce Shopify website developer – Jibrilsoft Website & Ecommerce Devel…”.

There are 2 <h1> headlines (“” and “Websites That Drive Growth, Sales & Performance”). One clear main headline is easier for people and search engines.

The homepage links to 86 pages on jibrilsoft.com and 4 external pages.

https://jibrilsoft.com/pages/gen122 has no meta description, so Google writes the search snippet from whatever text it finds.

https://jibrilsoft.com/pages/contact-us has no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

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