hotpack.com.sa website review

11 images could be 5.7 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 20.2 s faster on a phone.

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

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

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

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

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

8 third-party services load with your homepage (pop-convert.com, Google Tag Manager and Shopify and others), adding 1.7 MB and 1.2 s of main-thread time.

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

pop-convert.com costs a phone 384 ms of main-thread work and 310 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 Tag Manager costs a phone 206 ms of main-thread work and 348 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.

Shopify costs a phone 135 ms of main-thread work and 428 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.

Polyfills for old browsers add 22 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

About 40 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.

2 KiB JavaScript is shipped twice across bundles.

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.

Your largest element takes 42.2 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 48.5 s. Good is under 3.8 s.

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

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

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

Real visitors wait 355 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.

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

Real visitors wait 858 ms for your server to start answering (75th percentile). Good is under 800 ms.

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

Scripts block taps and scrolling for 209 ms in total while the page loads. Good is under 200 ms.

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

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

Your homepage downloads 11.6 MB in 575 requests on a phone: images 8.7 MB (329), scripts 1.6 MB (94) and other files 826 KiB (96). Under 2 MB keeps phones on slow connections fast.

4 images weigh 6.5 MB together. On a phone connection a single image that size takes seconds.

4 images (6.5 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.

mob_ARAB_7.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

1 image is downloaded at several times the size a phone draws it, for example mob_ARAB_7.jpg at 1,911 px wide, shown at 370 px. Resized copies would save about 86 KiB.

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

43 buttons have no accessible name, so screen readers announce just “button”.

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

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

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 11 elements on the page fail 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.

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

ARIA input fields do not have accessible names (1 element).

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

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

Your title is 85 characters, so Google will cut it off around 60: “Hotpack | #1 Manufacturer of Food Packaging Products in Saudi Arabia – hotpack.com.sa”.

No XML sitemap at https://hotpack.com.sa/sitemap.xmlUser-agent: *, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

The homepage links to 322 pages on hotpack.com.sa and 18 external pages.

https://hotpack.com.sa/collections/paper-products, https://hotpack.com.sa/collections/paper-takeway-boxes and https://hotpack.com.sa/collections/wet-wipes have no meta description, so Google writes the search snippet from whatever text it finds.

https://hotpack.com.sa/collections/tissue-products and https://hotpack.com.sa/collections/paper-napkins took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://hotpack.com.sa/cdn/shop/files/ramadan.png?v=14388.

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

5 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

18 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

The homepage carries about 684 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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 24 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 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.