Website review, no card needed
halfdaytravel.com website review
Visit site (opens in a new tab)Reviewed 4 November 202634 issues · 82 checks
This review found 34 issues worth fixing on halfdaytravel.com, 12 of them high impact, across 82 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
78C- #62,626 of 125,191 reviewed websitesbeats 45%
- #40,741 of 70,131 online storesbeats 36%
- #38,889 of 63,730 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.7 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.4 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 130 ms |
| May 23, 2026 | 130 ms |
| May 30, 2026 | 134 ms |
| Jun 6, 2026 | 137 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 138 ms |
| Jun 27, 2026 | 141 ms |
| Jul 4, 2026 | 146 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 160 ms |
| Jul 25, 2026 | 162 ms |
| Aug 1, 2026 | 163 ms |
| Aug 8, 2026 | 162 ms |
| Aug 15, 2026 | 163 ms |
| Aug 22, 2026 | 169 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 171 ms |
| Sep 19, 2026 | 171 ms |
| Sep 26, 2026 | 171 ms |
| Oct 3, 2026 | 173 ms |
| Oct 10, 2026 | 174 ms |
| Oct 17, 2026 | 176 ms |
| Oct 24, 2026 | 173 ms |
| Oct 31, 2026 | 171 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
1.2 s
2.3 s
3.5 s
4.7 s
5.8 s
7.0 s
8.2 s
9.4 s
Speed
Reduce unused JavaScript
2.0 s · 982 KiBAbout 982 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Use efficient cache lifetimes
1.2 s · 525 KiB35 files are served with short cache lifetimes, so returning visitors download them again (525 KiB).
Shopify adds 1.7 s
1.7 sShopify costs a phone 1.7 s of main-thread work and 212 KiB 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.
Main-thread work: 15.9 s
A phone's processor spends 15.9 s on main-thread work while loading, 8.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 38
38/100Your mobile performance score is 38. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and alia-prod.com and others), adding 2.5 MB and 3.6 s of main-thread time.
Improve image delivery
150 ms · 670 KiB21 images could be 670 KiB 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.
Google Tag Manager adds 551 ms
551 msGoogle Tag Manager costs a phone 551 ms of main-thread work and 528 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
450 ms · 152 KiBPolyfills for old browsers add 152 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
alia-prod.com adds 510 ms
510 msalia-prod.com costs a phone 510 ms of main-thread work and 784 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.
Render-blocking requests
400 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 400 ms.
2,731 HTML elements
The page has 2,731 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 263 ms. During a long task the page ignores taps.
rebuyengine.com adds 182 ms
182 msrebuyengine.com costs a phone 182 ms of main-thread work and 329 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 CSS
140 ms · 52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
48 KiB48 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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.3 s
16.3 sYour largest element takes 16.3 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: 29.9 s
29.9 sThe page becomes fully interactive after 29.9 s. Good is under 3.8 s.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 1.4 s
1.4 sScripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.
Tap response (INP) got 32% slower for real visitors
+32%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 130 ms to 171 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.5 s
2.5 sThe first text or image appears after 2.5 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.
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.7 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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: 2.0 s
2.0 sReal visitors wait 2.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 171 ms
171 msReal visitors wait 171 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: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 762 ms
762 msReal visitors wait 762 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.008
0.008The layout barely moves while loading (CLS 0.008, good is under 0.1).
Images and page weight
Page weight: 23.3 MB in 558 requests
23.3 MBYour homepage downloads 23.3 MB in 558 requests on a phone: media 17.0 MB (2), scripts 2.6 MB (112) and images 1.7 MB (91). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (34 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 6.6 g of CO₂ per visit
6.59 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.59 g of CO₂e: 791.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
3 tap targets too small
3 tap targets are too small or too close together to hit reliably with a finger.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate 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).
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
47 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: 47 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (70 characters)
Your title is 70 characters, so Google will cut it off around 60: “Halfday | Award-Winning 2-in-1 Garment Duffel | 4.7/5 and 5000+reviews”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://halfdaytravel.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at halfdaytravel.com/robots.txt, the first file search crawlers ask for.
53 internal links, 15 external
The homepage links to 53 pages on halfdaytravel.com and 15 external pages.
4 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “2-in-1 garment duffels and luggage for wrinkle-free travel. Carry-on compliant. Featured in Forbes & Esquire. 5,000+ re…”.
One H1 headline
Your main headline reads: “Halfday”.
Canonical URL set
The canonical URL is https://halfdaytravel.com/.
Structured data in place
Structured data found: OnlineStore, WebPage and WebSite.
AI search readiness
No llms.txt
There is no https://halfdaytravel.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
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 (683 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://halfdaytravel.com/products/garment-duffel-premium has 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 24 found) and read each the way a search engine does.
6 checks passed
Linked pages load
4 pages of 15 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.
Every page has a meta description
All 4 pages that loaded have a meta description.
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 4 pages that loaded have a <title>.
Best practices
46 small tap targets
46 of 101 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 “Failed to load resource: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 11 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 864 words of copy
The homepage carries about 864 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: “Shop the Spinner”.
6 calls to action
The homepage has 6 calls to action, for example “Shop the Spinner”, “Shop Now” and “Shop The Cabin Bag”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and LinkedIn Insight and 3 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
33 cookies set on arrival
33Opening the homepage sets 33 cookies (measured from a US location before any click).
55 other companies contacted
Loading the homepage contacts 55 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
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 halfdaytravel.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 19 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Attentive · Triplewhale · Eko Interactive Video · The Rave · Klaviyo Email Marketing Sms · Checkmate · Vo Product Options · Starapps Variant Image · Userway Website Accessibility · Applovin Shop Integration · Variable Products · nice-team.net · liadm.com · attn.tv · amazonaws.com · retention.com · goaffpro.com · rebuyengine.com · useamp.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
Stack
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on halfdaytravel.com, including 21 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.