Website review, no card needed

alpino.store logo

alpino.store website review

Visit site (opens in a new tab)Reviewed 19 October 202646 issues · 94 checks

This review found 46 issues worth fixing on alpino.store, 12 of them high impact, across 94 checks. The most urgent: 3 images over 500 KB. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
3.7 s2.7 sMay 2Oct 173.3 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.9 s
May 9, 20262.9 s
May 16, 20262.9 s
May 23, 20262.9 s
May 30, 20263.0 s
Jun 6, 20263.0 s
Jun 13, 20263.1 s
Jun 20, 20262.9 s
Jun 27, 20262.9 s
Jul 4, 20262.9 s
Jul 11, 20262.8 s
Jul 18, 20262.8 s
Jul 25, 20263.0 s
Aug 1, 20263.0 s
Aug 8, 20263.0 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.4 s
Sep 12, 20263.5 s
Sep 19, 20263.6 s
Sep 26, 20263.5 s
Oct 3, 20263.4 s
Oct 10, 20263.3 s
Oct 17, 20263.3 s
Real-visitor tap response (INP)75th percentile, phones
224 ms191 msMay 2Oct 17220 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026220 ms
May 9, 2026215 ms
May 16, 2026209 ms
May 23, 2026204 ms
May 30, 2026203 ms
Jun 6, 2026205 ms
Jun 13, 2026205 ms
Jun 20, 2026212 ms
Jun 27, 2026210 ms
Jul 4, 2026208 ms
Jul 11, 2026207 ms
Jul 18, 2026197 ms
Jul 25, 2026195 ms
Aug 1, 2026202 ms
Aug 8, 2026209 ms
Aug 15, 2026213 ms
Aug 22, 2026215 ms
Aug 29, 2026214 ms
Sep 5, 2026211 ms
Sep 12, 2026212 ms
Sep 19, 2026213 ms
Sep 26, 2026215 ms
Oct 3, 2026219 ms
Oct 10, 2026219 ms
Oct 17, 2026220 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

Full-page screenshot of alpino.store (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. alpino.store at 1.2 s1.2 s
  2. alpino.store at 2.4 s2.4 s
  3. alpino.store at 3.7 s3.7 s
  4. alpino.store at 4.9 s4.9 s
  5. alpino.store at 6.1 s6.1 s
  6. alpino.store at 7.3 s7.3 s
  7. alpino.store at 8.5 s8.5 s
  8. alpino.store at 9.8 s9.8 s

Speed

13 to fix37
  • Mobile performance score: 37

    37/100

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

  • Main-thread work: 8.6 s

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

  • 6,232 HTML elements

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Shopify and Facebook and others), adding 5.2 MB and 1.9 s of main-thread time.

  • Improve image delivery

    1.4 MB

    54 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Google Tag Manager adds 833 ms

    833 ms

    Google Tag Manager costs a phone 833 ms of main-thread work and 989 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

    928 KiB

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

  • Use efficient cache lifetimes

    815 KiB

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

  • Shopify adds 343 ms

    343 ms

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

  • Reduce unused CSS

    300 ms · 134 KiB

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

  • Facebook adds 286 ms

    286 ms

    Facebook costs a phone 286 ms of main-thread work and 282 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.

  • 20 long tasks on the main thread

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

  • gokwik.co adds 169 ms

    169 ms

    gokwik.co costs a phone 169 ms of main-thread work and 508 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.

  • Font display

    150 ms

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

  • Legacy JavaScript

    58 KiB

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

  • Duplicated JavaScript

    15 KiB

    15 KiB JavaScript is shipped twice across bundles.

  • Minify CSS

    12 KiB

    12 KiB could be saved by minifying CSS.

  • Minify JavaScript

    8 KiB

    8 KiB could be saved by minifying JavaScript.

  • 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: 41 ms

    41 ms

    Your server sent the HTML in 41 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • 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: 37.1 s

    37.1 s

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

  • Speed Index: 14.2 s

    14.2 s

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

  • Largest Contentful Paint: 8.0 s

    8.0 s

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

  • Total Blocking Time: 1.1 s

    1.1 s

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

  • Real-user LCP: 3.1 s

    3.1 s

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

  • Real-user INP: 243 ms

    243 ms

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

  • Real-user FCP: 2.5 s

    2.5 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +1%

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

  • Largest content (LCP) got 14% slower for real visitors

    +14%

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

2 checks passed
  • Real-user CLS: 0.10

    0.10

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

  • Cumulative Layout Shift: 0.092

    0.092

    The layout barely moves while loading (CLS 0.092, good is under 0.1).

Images and page weight

5 to fix36
  • 3 images over 500 KB

    3 images weigh 9.2 MB together. On a phone connection a single image that size takes seconds.

  • Page weight: 9.2 MB in 434 requests

    9.2 MB

    Your homepage downloads 9.2 MB in 434 requests on a phone: images 4.2 MB (117), scripts 2.4 MB (117) and media 1,002 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 38 images in older formats

    38 images (12.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.

  • An image on the first screen is lazy-loaded

    Dark_Chocolate_Oats_1kg_Banner_Mobile.webp 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 far larger than shown

    7 KiB

    1 image is downloaded at several times the size a phone draws it, for example mvp-divider_cfdd76ea-f565-4bcf-b665-887d82914193.svg at 1,920 px wide, shown at 624 px. Resized copies would save about 7 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (226 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.6 g of CO₂ per visit

    2.60 g

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

Accessibility

6 to fix76
  • 32 images without alt text

    32 images have no alt text, which hurts accessibility and image search.

  • Zoom is disabled

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

  • 65 form fields without a label

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

  • 25 text elements with low contrast

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

  • 6 tap targets too small

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

  • 3 links without text

    3 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (5 elements).

SEO

3 to fixGoogle 8588
  • Meta description is long (172 characters)

    Your meta description is 172 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 3 links with vague text

    3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • One H1 headline

    Your <h1> is empty.

  • 116 internal links, 10 external

    The homepage links to 116 pages on alpino.store and 10 external pages.

6 checks passed
  • Title: 63 characters

    Your title is a healthy 63 characters: “Buy Fresh & Healthy India's Best Peanut Product Online - Alpino”.

  • Canonical URL set

    The canonical URL is https://alpino.store/.

  • Structured data in place

    Structured data found: BreadcrumbList, Organization 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://alpino.store/sitemap.xml.

AI search readiness

100
4 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, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,918 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://alpino.store/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 5 pages without a meta description

    https://alpino.store/collections/new-arrivals, https://alpino.store/collections/masala-oats, https://alpino.store/collections/super-bars, https://alpino.store/collections/essentials and https://alpino.store/collections/combo-sale have no meta description, so Google writes the search snippet from whatever text it finds.

  • 14 pages without an H1

    https://alpino.store/pages/membership, https://alpino.store/pages/become-a-distributor, https://alpino.store/pages/our-story, https://alpino.store/collections/new-arrivals, https://alpino.store/collections/all-products and https://alpino.store/collections/peanut-butter and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 45 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 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7391
  • 3 third-party cookies

    3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'replaceChild')”.

  • Browser-reported issues

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

2 checks passed
  • Tap targets are thumb-sized

    64 of 70 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix81
  • 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.

  • 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 1,285 words of copy

    The homepage carries about 1,285 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Contact Us”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Track Order”, “CONTACT US” and “TRACK ORDER”.

  • 38 short forms

    38 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 82 testimonial or review blocks and 1 customer or partner logo.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    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.

  • 41 cookies set on arrival

    41

    Opening the homepage sets 41 cookies (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.

  • 53 other companies contacted

    Loading the homepage contacts 53 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 alpino.store, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Analytics | Google Tag Manager | Microsoft Clarity

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 46 issues on alpino.store, including 24 speed issues, 3 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25