Website review, no card needed
ovejanegrabikepacking.com website review
Visit site (opens in a new tab)Reviewed 21 October 202632 issues · 78 checks
This review found 32 issues worth fixing on ovejanegrabikepacking.com, 11 of them high impact, across 78 checks. The most urgent: improve image delivery. 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
79C- #55,423 of 124,112 reviewed websitesbeats 50%
- #36,434 of 69,786 online storesbeats 42%
- #34,903 of 63,472 Shopify storesbeats 39%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 601 ms |
| May 9, 2026 | 644 ms |
| May 16, 2026 | 655 ms |
| May 23, 2026 | 658 ms |
| May 30, 2026 | 635 ms |
| Jun 6, 2026 | 613 ms |
| Jun 13, 2026 | 618 ms |
| Jun 20, 2026 | 630 ms |
| Jun 27, 2026 | 641 ms |
| Jul 4, 2026 | 673 ms |
| Jul 11, 2026 | 679 ms |
| Jul 18, 2026 | 664 ms |
| Jul 25, 2026 | 667 ms |
| Aug 1, 2026 | 667 ms |
| Aug 8, 2026 | 678 ms |
| Aug 15, 2026 | 658 ms |
| Aug 22, 2026 | 667 ms |
| Aug 29, 2026 | 669 ms |
| Sep 5, 2026 | 650 ms |
| Sep 12, 2026 | 669 ms |
| Sep 19, 2026 | 669 ms |
| Sep 26, 2026 | 659 ms |
| Oct 3, 2026 | 664 ms |
| Oct 10, 2026 | 678 ms |
| Oct 17, 2026 | 664 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 62 ms |
| May 9, 2026 | 63 ms |
| May 16, 2026 | 64 ms |
| May 23, 2026 | 66 ms |
| May 30, 2026 | 64 ms |
| Jun 6, 2026 | 63 ms |
| Jun 13, 2026 | 63 ms |
| Jun 20, 2026 | 63 ms |
| Jun 27, 2026 | 63 ms |
| Jul 4, 2026 | 63 ms |
| Jul 11, 2026 | 63 ms |
| Jul 18, 2026 | 62 ms |
| Jul 25, 2026 | 62 ms |
| Aug 1, 2026 | 62 ms |
| Aug 8, 2026 | 63 ms |
| Aug 15, 2026 | 63 ms |
| Aug 22, 2026 | 64 ms |
| Aug 29, 2026 | 65 ms |
| Sep 5, 2026 | 64 ms |
| Sep 12, 2026 | 64 ms |
| Sep 19, 2026 | 64 ms |
| Sep 26, 2026 | 63 ms |
| Oct 3, 2026 | 63 ms |
| Oct 10, 2026 | 63 ms |
| Oct 17, 2026 | 63 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
How it loaded on a phone
0.6 s
1.1 s
1.7 s
2.2 s
2.8 s
3.3 s
3.9 s
4.4 s
Speed
Improve image delivery
3.3 s · 688 KiB7 images could be 688 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
1.4 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 60
60/100Your mobile performance score is 60 (desktop: 75). Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
600 ms · 74 KiBAbout 74 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
650 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 650 ms).
6 third-party services on the page
6 third-party services load with your homepage (Shopify, Google CDN and Yotpo and others), adding 1.0 MB and 217 ms of main-thread time.
Shopify adds 143 ms
143 msShopify costs a phone 143 ms of main-thread work and 949 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.
Use efficient cache lifetimes
150 ms · 15 KiB4 files are served with short cache lifetimes, so returning visitors download them again (15 KiB).
Reduce unused CSS
17 KiBAbout 17 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
6 KiBPolyfills for old browsers add 6 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.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 412 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 18.8 s
18.8 sYour largest element takes 18.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.6 s
3.6 sThe first text or image appears after 3.6 s on a phone. Good is under 1.8 s.
2 images without width and height
2 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 62 ms to 63 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 0.6 s to 0.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 58 ms
58 msReal visitors wait 58 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 404 ms
404 msReal visitors wait 404 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
1 image over 500 KB
newhomepagebike.jpg weighs 489 KiB. On a phone connection a single image that size takes seconds.
Page weight: 3.1 MB in 151 requests
3.1 MBYour homepage downloads 3.1 MB in 151 requests on a phone: images 1.7 MB (13), other files 842 KiB (86) and scripts 497 KiB (43). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
440 KiB1 image is downloaded at several times the size a phone draws it, for example newhomepagebike.jpg at 3,400 px wide, shown at 360 px. Resized copies would save about 440 KiB.
1 image in older formats
1 image (31 KiB) is 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 (67 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.87 g of CO₂e: 104.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 7 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (318 characters)
Your meta description is 318 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
64 internal links, 4 external
The homepage links to 64 pages on ovejanegrabikepacking.com and 4 external pages.
5 checks passed
Title: 63 characters
Your title is a healthy 63 characters: “Oveja Negra Adventure Cycling Gear and Bike Bags – Oveja Negra™”.
Canonical URL set
The canonical URL is https://www.ovejanegrabikepacking.com/.
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://www.ovejanegrabikepacking.com/sitemap.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.
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.
llms.txt published
The site publishes https://www.ovejanegrabikepacking.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
13 pages without a meta description
https://www.ovejanegrabikepacking.com/collections/all, https://www.ovejanegrabikepacking.com/collections/new-1, https://www.ovejanegrabikepacking.com/collections/frame-bags, https://www.ovejanegrabikepacking.com/collections/seat-bags, https://www.ovejanegrabikepacking.com/collections/top-tube-bags and https://www.ovejanegrabikepacking.com/collections/handlebar-bags and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages with very little text
https://www.ovejanegrabikepacking.com/collections/new-1, https://www.ovejanegrabikepacking.com/collections/seat-bags and https://www.ovejanegrabikepacking.com/collections/sale have 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
6 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.
Every page has an H1
Each page we checked has a main headline.
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
12 small tap targets
12 of 24 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 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 ()”.
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 social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 44 words
The homepage has only about 44 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
1 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact”.
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.
13 cookies set on arrival
13Opening the homepage sets 13 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.
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 ovejanegrabikepacking.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on ovejanegrabikepacking.com, including 12 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.