Website review, no card needed
hotpack.om website review
Visit site (opens in a new tab)Reviewed 20 November 202645 issues · 92 checks
This review found 45 issues worth fixing on hotpack.om, 18 of them high impact, across 92 checks. The most urgent: shopify adds 12.0 s. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
63D- #118,443 of 124,749 reviewed websitesbeats 4%
- #68,461 of 70,019 online storesbeats 2%
- #62,514 of 63,642 Shopify storesbeats 1%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.3 s |
| Jul 11, 2026 | 3.3 s |
| Jul 18, 2026 | 3.4 s |
| Jul 25, 2026 | 3.4 s |
| Aug 1, 2026 | 3.3 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.2 s |
| Aug 29, 2026 | 3.4 s |
| Sep 5, 2026 | 3.3 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.5 s |
| Oct 24, 2026 | 3.3 s |
| Oct 31, 2026 | 3.3 s |
| Nov 7, 2026 | 3.3 s |
| Nov 14, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 284 ms |
| Jun 6, 2026 | 292 ms |
| Jun 13, 2026 | 304 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 247 ms |
| Jul 4, 2026 | 246 ms |
| Jul 11, 2026 | 249 ms |
| Jul 18, 2026 | 266 ms |
| Jul 25, 2026 | 271 ms |
| Aug 1, 2026 | 246 ms |
| Aug 8, 2026 | 238 ms |
| Aug 15, 2026 | 239 ms |
| Aug 22, 2026 | 235 ms |
| Aug 29, 2026 | 253 ms |
| Sep 5, 2026 | 249 ms |
| Sep 12, 2026 | 238 ms |
| Sep 19, 2026 | 245 ms |
| Sep 26, 2026 | 243 ms |
| Oct 3, 2026 | 243 ms |
| Oct 10, 2026 | 242 ms |
| Oct 17, 2026 | 231 ms |
| Oct 24, 2026 | 231 ms |
| Oct 31, 2026 | 215 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Shopify adds 12.0 s
12.0 sShopify costs a phone 12.0 s of main-thread work and 453 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Main-thread work: 26.8 s
A phone's processor spends 26.8 s on main-thread work while loading, 18.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Render-blocking requests
1.8 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.8 s.
14,347 HTML elements
The page has 14,347 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 30
30/100Your mobile performance score is 30. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and Key CDN and others), adding 1.1 MB and 12.6 s of main-thread time.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 3.5 s. During a long task the page ignores taps.
Improve image delivery
50 ms · 2.2 MB18 images could be 2.2 MB 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.
Reduce unused JavaScript
240 KiBAbout 240 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
61 KiB12 files are served with short cache lifetimes, so returning visitors download them again (61 KiB).
Reduce unused CSS
40 KiBAbout 40 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
22 KiBPolyfills for old browsers add 22 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
1 checks passed
Server response: 68 ms
68 msYour server sent the HTML in 68 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Largest Contentful Paint: 11.0 s
11.0 sYour largest element takes 11.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 10.6 s
10.6 sScripts block taps and scrolling for 10.6 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 33.1 s
33.1 sThe page becomes fully interactive after 33.1 s. Good is under 3.8 s.
Speed Index: 7.3 s
7.3 sVisually, the page fills in at 7.3 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.2 s
3.2 sThe first text or image appears after 3.2 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.1 s
3.1 sReal visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.6 s
2.6 sReal visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.5 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user TTFB: 684 ms
684 msReal visitors wait 684 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 284 ms to 215 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.09
0.09The layout barely moves while loading (CLS 0.09, good is under 0.1).
Images and page weight
Page weight: 7.5 MB in 583 requests
7.5 MBYour homepage downloads 7.5 MB in 583 requests on a phone: images 5.2 MB (349), scripts 966 KiB (88) and other files 842 KiB (93). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.11 g of CO₂e: 253.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
ARIA commands must have an accessible name (7 elements)
ARIA commands must have an accessible name: 7 elements on the page fail this check, rated serious by axe-core.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
45 buttons without a name
45 buttons have no accessible name, so screen readers announce just “button”.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
ARIA input fields do not have accessible names
ARIA input fields do not have accessible names (5 elements).
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
Elements use prohibited ARIA attributes
Elements use prohibited ARIA attributes (1 element).
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (8 elements)
ARIA role should be appropriate for the element: 8 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
SVG elements with an img role do not have an accessible text alternative
SVG elements with an img role do not have an accessible text alternative (8 elements).
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (90 characters)
Your title is 90 characters, so Google will cut it off around 60: “الشركة المصنعة والموردة رقم #1 لمنتجات تعبئة وتغليف المواد الغذائية في عمان – Hotpack Oman”.
Meta description is long (182 characters)
Your meta description is 182 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
448 internal links, 30 external
The homepage links to 448 pages on hotpack.om and 30 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Hotpack Oman”.
Canonical URL set
The canonical URL is https://hotpack.om/.
Structured data in place
Structured data found: LocalBusiness, Organization and WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://hotpack.om/sitemap.xml.
AI search readiness
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles) and contact details; logo and description would complete it.
llms.txt published
The site publishes https://hotpack.om/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://hotpack.om/collections/flat-handle-paper-bags has no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://hotpack.om/collections/paper-products-1 has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://hotpack.om/collections/paper-products-1 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.
1 page slow to respond
https://hotpack.om/collections/kraft-paper-cups took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 183 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 503 ()”.
18 distorted images
18 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
24 of 25 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 18 words
The homepage has only about 18 words of visible text; thin pages give Google and first-time buyers little to go on.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
5 checks passed
1 call to action
The homepage has 1 call to action, for example “Best Buy”.
25 short forms
25 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
9 cookies set on arrival
9Opening the homepage sets 9 cookies, 5 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
4 other companies contacted
Loading the homepage contacts 4 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at hotpack.om, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Frequently Bought · Candy Rack · Microsoft Clarity · Judge Me Reviews · Tms Prod V 71ff83e · zoko.io · snapchat.com · kxcdn.com · Selleasy
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Analytics | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on hotpack.om, including 16 speed issues, 4 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.