Website review, no card needed
jumbo.al website review
Visit site (opens in a new tab)Reviewed 30 October 202652 issues · 97 checks
This review found 52 issues worth fixing on jumbo.al, 14 of them high impact, across 97 checks. The most urgent: render-blocking requests. 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
81BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.5 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.4 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.4 s |
| Jun 20, 2026 | 2.3 s |
| Jun 27, 2026 | 2.3 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.2 s |
| Aug 1, 2026 | 2.2 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.2 s |
| Aug 22, 2026 | 2.1 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.2 s |
| Sep 12, 2026 | 2.2 s |
| Sep 19, 2026 | 2.2 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 119 ms |
| May 16, 2026 | 119 ms |
| May 23, 2026 | 119 ms |
| May 30, 2026 | 119 ms |
| Jun 6, 2026 | 121 ms |
| Jun 13, 2026 | 119 ms |
| Jun 20, 2026 | 117 ms |
| Jun 27, 2026 | 117 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 121 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 129 ms |
| Aug 1, 2026 | 131 ms |
| Aug 8, 2026 | 124 ms |
| Aug 15, 2026 | 116 ms |
| Aug 22, 2026 | 107 ms |
| Aug 29, 2026 | 99 ms |
| Sep 5, 2026 | 102 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 99 ms |
| Oct 3, 2026 | 95 ms |
| Oct 10, 2026 | 91 ms |
| Oct 17, 2026 | 88 ms |
| Oct 24, 2026 | 87 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
Render-blocking requests
1.4 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
4,203 HTML elements
The page has 4,203 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
150 ms · 3.6 MB38 images could be 3.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
2.6 MB17 files are served with short cache lifetimes, so returning visitors download them again (2.6 MB).
8 third-party services on the page
8 third-party services load with your homepage (gy.digital, Google Tag Manager and findbar.io and others), adding 5.2 MB and 837 ms of main-thread time.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
gy.digital adds 364 ms
364 msgy.digital costs a phone 364 ms of main-thread work and 4.7 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.
Google Tag Manager adds 363 ms
363 msGoogle Tag Manager costs a phone 363 ms of main-thread work and 331 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.
Reduce unused JavaScript
393 KiBAbout 393 KiB of JavaScript is downloaded but never used on this page.
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 297 ms. During a long task the page ignores taps.
Reduce unused CSS
51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 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: 231 ms
231 msYour server sent the HTML in 231 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.
Time to Interactive: 11.5 s
11.5 sThe page becomes fully interactive after 11.5 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Real-user TTFB: 911 ms
911 msReal visitors wait 911 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 549 ms
549 msScripts block taps and scrolling for 549 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.7 s
2.7 sYour largest element takes 2.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “HALLOWEEN NEW”.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.5 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Tap response (INP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 119 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.025
0.025The layout barely moves while loading (CLS 0.025, good is under 0.1).
Images and page weight
Page weight: 5.5 MB in 129 requests
5.5 MBYour homepage downloads 5.5 MB in 129 requests on a phone: images 4.5 MB (60), scripts 829 KiB (13) and other files 61 KiB (49). Under 2 MB keeps phones on slow connections fast.
16 images far larger than shown
3.8 MB16 images are downloaded at several times the size a phone draws them, for example rxnuxh3oacrbcp0qpl0gun5mzhwk-Untitled design (8).png at 835 px wide, shown at 60 px. Resized copies would save about 3.8 MB.
2 images over 500 KB
2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.
10 images in older formats
10 images (3.8 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.
2 images below the first screen load straight away
2 images further down the page (63 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.6 g of CO₂ per visit
1.56 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.56 g of CO₂e: 187.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (96 elements)
All page content should be contained by landmarks: 96 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
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.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (9 elements)
Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 12 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (27 characters)
Your title is only 27 characters: “Jumbo - Bota e Buzëqeshjeve”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://jumbo.al/sitemap_alb.xml.gz, so Google discovers your pages only by following links.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
452 internal links, 17 external
The homepage links to 452 pages on jumbo.al and 17 external pages.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Bli online duke zgjedhur mes 30.000 produktesh: lodra dhe artikuj për fëmijë, dekorime dhe organizim i shtëpisë si dhe …”.
Canonical URL set
The canonical URL is https://www.jumbo.al/sq.
Structured data in place
Structured data found: Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No llms.txt
There is no https://jumbo.al/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.
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (1,625 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages share a title
https://jumbo.al/sq, https://jumbo.al/stores, https://jumbo.al/sq/track, https://jumbo.al/sq/order and https://jumbo.al/sq/catalog all use the title “Jumbo - Bota e Buzëqeshjeve”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://jumbo.al/stores, https://jumbo.al/sq/track, https://jumbo.al/sq/order and https://jumbo.al/sq/catalog have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://jumbo.al/stores, whose canonical is https://jumbo.al/sq/stores. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
14 pages without an H1
https://jumbo.al/stores, https://jumbo.al/sq/track, https://jumbo.al/en, https://jumbo.al/sq/order, https://jumbo.al/sq/catalog/produkte-te-reja and https://jumbo.al/sq/catalog/artikuj-sezonale-halloween and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://jumbo.al/sq/catalog/produkte-per-bebe, https://jumbo.al/sq/catalog/dekorimi-i-shtepise, https://jumbo.al/sq/catalog/kuzhina and https://jumbo.al/sq/catalog/shkolla took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 188 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
28 small tap targets
28 of 100 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://s3.gy.digital/jumbo_al/storage/i1chxkpuz2i4uwnteqldnlcpr4lp-kitchen_fixed.svg' fro…”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
1 checks passed
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 620 words of copy
The homepage carries about 620 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “{{ order.total_quantity }} Shporta”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
12 other companies contacted
Loading the homepage contacts 12 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 jumbo.al, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- Analytics
- Google Tag Manager
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on jumbo.al, including 19 speed issues, 3 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.