Website review, no card needed
alpina.com website review
Visit site (opens in a new tab)Reviewed 19 October 202651 issues · 84 checks
This review found 51 issues worth fixing on alpina.com, 24 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
61D- #115,858 of 119,769 reviewed websitesbeats 3%
- #67,075 of 67,907 online storesbeats 1%
- #634 of 713 Magento storesbeats 9%
Closest competitors among Magento stores
Compare side by sideOne score from every part of this review. How it works
Speed
Reduce unused JavaScript
8.7 s · 1.4 MBAbout 1.4 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 8.7 s faster on a phone.
Google Tag Manager adds 1.6 s
1.6 sGoogle Tag Manager costs a phone 1.6 s of main-thread work and 1.2 MB 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.
Render-blocking requests
1.6 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Use efficient cache lifetimes
1.4 s · 295 KiB6 files are served with short cache lifetimes, so returning visitors download them again (295 KiB).
Reduce unused CSS
1.2 s · 248 KiBAbout 248 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 27
27/100Your mobile performance score is 27 (desktop: 26). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and Facebook and others), adding 2.7 MB and 2.8 s of main-thread time.
Improve image delivery
2.3 MB17 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 526 ms. During a long task the page ignores taps.
Google CDN adds 335 ms
335 msGoogle CDN costs a phone 335 ms of main-thread work and 730 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.
Legacy JavaScript
300 ms · 76 KiBPolyfills for old browsers add 76 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.
Facebook adds 312 ms
312 msFacebook costs a phone 312 ms of main-thread work and 279 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.
TikTok adds 271 ms
271 msTikTok costs a phone 271 ms of main-thread work and 273 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.
1,976 HTML elements
The page has 1,976 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 16 KiB16 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.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 31 ms
31 msYour server sent the HTML in 31 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.0 s
12.0 sThe first text or image appears after 12.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 53.8 s
53.8 sYour largest element takes 53.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 24.2 s
24.2 sVisually, the page fills in at 24.2 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 57.3 s
57.3 sThe page becomes fully interactive after 57.3 s. Good is under 3.8 s.
Total Blocking Time: 2.0 s
2.0 sScripts block taps and scrolling for 2.0 s in total while the page loads. Good is under 200 ms.
13 images without width and height
13 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 13.7 MB in 491 requests
13.7 MBYour homepage downloads 13.7 MB in 491 requests on a phone: images 9.2 MB (157), scripts 3.6 MB (249) and other files 414 KiB (69). Under 2 MB keeps phones on slow connections fast.
4 images over 500 KB
4 images weigh 3.5 MB together. On a phone connection a single image that size takes seconds.
13 images below the first screen load straight away
13 images further down the page (2.0 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
63 KiB1 image is downloaded at several times the size a phone draws it, for example banner-colab-styker-mb-1-1.png at 1,536 px wide, shown at 307 px. Resized copies would save about 63 KiB.
3 images in older formats
3 images (218 KiB) 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.
About 3.9 g of CO₂ per visit
3.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.87 g of CO₂e: 464.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
ARIA dialog and alertdialog nodes should have an accessible name (1 element)
ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
Interactive controls must not be nested (1 element)
Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
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.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 7 failed. 3 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 long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Alimentos y contenidos nutritivos | Alpina Colombia por un mundo delicioso”.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (167 characters)
Your meta description is 167 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (untyped) but with 1 problem, for example “ld+json block 1 is not valid JSON (Bad control character in string literal in JSON at position )”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
288 internal links, 40 external
The homepage links to 288 pages on alpina.com and 40 external pages.
2 checks passed
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://alpina.com//media/sitemap/sitemap_alpinabogota.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://alpina.com/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (1,483 words), so crawlers that don't run JavaScript still read it.
Other pages
9 pages without a meta description
https://alpina.com/aprende-de-nutricion, https://alpina.com/profesionales-de-la-salud, https://alpina.com/cuentos-de-nutricion, https://alpina.com/sostenibilidad/informes, https://alpina.com/nuestra-historia and https://alpina.com/gen-a and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://alpina.com/aprende-de-nutricion, https://alpina.com/profesionales-de-la-salud, https://alpina.com/gen-a and https://alpina.com/bonyurt-en-punto 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 145 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
3 small tap targets
3 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
6 distorted images
6 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 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 439 words of copy
The homepage carries about 439 words of visible text.
3 checks passed
4 short forms
4 short forms (2 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel 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.
40 cookies set on arrival
40Opening the homepage sets 40 cookies, 4 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.
38 other companies contacted
Loading the homepage contacts 38 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 alpina.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Magento
- Analytics
- Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 51 issues on alpina.com, including 21 speed issues, 7 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.