Website review, no card needed
beaglland.com website review
Visit site (opens in a new tab)Reviewed 12 November 202628 issues · 69 checks
This review found 28 issues worth fixing on beaglland.com, 7 of them high impact, across 69 checks. The most urgent: page weight: 28.7 MB in 158 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
One score from every part of this review. How it works
Speed
Reduce unused JavaScript
1.2 s · 262 KiBAbout 262 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (Google Tag Manager, Shopify and Heroku and others), adding 17.4 MB and 271 ms of main-thread time.
Shopify adds 87 ms
87 msShopify costs a phone 87 ms of main-thread work and 17.2 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.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused CSS
450 ms · 100 KiBAbout 100 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Improve image delivery
300 ms · 141 KiB3 images could be 141 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Use efficient cache lifetimes
350 ms · 79 KiB4 files are served with short cache lifetimes, so returning visitors download them again (79 KiB).
Legacy JavaScript
150 ms · 20 KiBPolyfills for old browsers add 20 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 145 ms. During a long task the page ignores taps.
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 490 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.2 s
7.2 sYour largest element takes 7.2 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: 7.4 s
7.4 sThe page becomes fully interactive after 7.4 s. Good is under 3.8 s.
Speed Index: 5.6 s
5.6 sVisually, the page fills in at 5.6 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 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.
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.
2 checks passed
Total Blocking Time: 132 ms
132 msScripts block the page for only 132 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 28.7 MB in 158 requests
28.7 MBYour homepage downloads 28.7 MB in 158 requests on a phone: media 27.0 MB (3), other files 687 KiB (85) and scripts 581 KiB (41). Under 2 MB keeps phones on slow connections fast.
2 images far larger than shown
11 KiB2 images are downloaded at several times the size a phone draws them, for example beaglland-index-section2.webp at 1,200 px wide, shown at 390 px. Resized copies would save about 11 KiB.
2 images in older formats
2 images (165 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.
1 image below the first screen load straight away
1 image further down the page (56 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 8.1 g of CO₂ per visit
8.13 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.13 g of CO₂e: 976.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 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 meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
One H1 headline
Your <h1> is empty.
19 internal links, 10 external
The homepage links to 19 pages on beaglland.com and 10 external pages.
5 checks passed
Title: 45 characters
Your title is a healthy 45 characters: “Beaglland -The Revolutionary Trolley Suitcase”.
Canonical URL set
The canonical URL is https://beaglland.com/.
Structured data in place
Structured data found: 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://beaglland.com/sitemap.xml.
AI search readiness
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 (325 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://beaglland.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://beaglland.com/collections/fitzroy-x1, https://beaglland.com/pages/shipping and https://beaglland.com/pages/warranty have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://beaglland.com/collections/fitzroy-x1 has no <h1> headline, so visitors and search engines get no clear main topic.
6 internal pages checked
We fetched 6 pages linked from your homepage and read each the way a search engine does.
5 checks passed
Linked pages load
5 pages of 6 loaded without an error (the rest turned automated requests away).
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 5 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 253 words of copy
The homepage carries about 253 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: “Learn More”.
2 calls to action
The homepage has 2 calls to action, for example “Learn More” and “Subscribe Now”.
3 short forms
3 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 1 email link.
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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
6 other companies contacted
Loading the homepage contacts 6 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 beaglland.com, 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 1 app. It is code from another company running for your shoppers.
Apps your storefront loads
herokuapp.com
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
- The footer still says © 2023.
Stack
- Framework
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on beaglland.com, including 13 speed issues, 4 SEO issues and 1 conversion gap. 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.