Website review, no card needed
joules.com website review
Visit site (opens in a new tab)Reviewed 25 October 202642 issues · 88 checks
This review found 42 issues worth fixing on joules.com, 18 of them high impact, across 88 checks. The most urgent: use efficient cache lifetimes. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.8 s |
| May 9, 2026 | 1.8 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.7 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 332 ms |
| May 9, 2026 | 326 ms |
| May 16, 2026 | 312 ms |
| May 23, 2026 | 303 ms |
| May 30, 2026 | 300 ms |
| Jun 6, 2026 | 302 ms |
| Jun 13, 2026 | 308 ms |
| Jun 20, 2026 | 313 ms |
| Jun 27, 2026 | 317 ms |
| Jul 4, 2026 | 320 ms |
| Jul 11, 2026 | 320 ms |
| Jul 18, 2026 | 320 ms |
| Jul 25, 2026 | 320 ms |
| Aug 1, 2026 | 319 ms |
| Aug 8, 2026 | 318 ms |
| Aug 15, 2026 | 319 ms |
| Aug 22, 2026 | 312 ms |
| Aug 29, 2026 | 310 ms |
| Sep 5, 2026 | 303 ms |
| Sep 12, 2026 | 294 ms |
| Sep 19, 2026 | 287 ms |
| Sep 26, 2026 | 279 ms |
| Oct 3, 2026 | 277 ms |
| Oct 10, 2026 | 279 ms |
| Oct 17, 2026 | 283 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
Speed
Use efficient cache lifetimes
3.5 s · 1.0 MB75 files are served with short cache lifetimes, so returning visitors download them again (1.0 MB).
Render-blocking requests
3.8 s26 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.8 s.
Reduce unused JavaScript
1.9 s · 966 KiBAbout 966 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Reduce unused CSS
1.2 s · 161 KiBAbout 161 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.
Google Tag Manager adds 1.2 s
1.2 sGoogle Tag Manager costs a phone 1.2 s of main-thread work and 1.1 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.
Mobile performance score: 40
40/100Your mobile performance score is 40 (desktop: 32). 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 (Google Tag Manager, Optanon and nextdirect.com and others), adding 3.7 MB and 1.4 s of main-thread time.
Improve image delivery
1.1 MB19 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Main-thread work: 4.0 s
A phone's processor spends 4.0 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 254 ms. During a long task the page ignores taps.
platform.next adds 3 ms
3 msplatform.next costs a phone 3 ms of main-thread work and 2.1 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.
1,708 HTML elements
The page has 1,708 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 34 KiBPolyfills for old browsers add 34 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
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.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
Minify CSS
3 KiB3 KiB could be saved by minifying CSS.
1 checks passed
Server response: 147 ms
147 msYour server sent the HTML in 147 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
Largest Contentful Paint: 13.9 s
13.9 sYour largest element takes 13.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “WELCOME TO AUTUMN”.
Time to Interactive: 25.5 s
25.5 sThe page becomes fully interactive after 25.5 s. Good is under 3.8 s.
First Contentful Paint: 5.0 s
5.0 sThe first text or image appears after 5.0 s on a phone. Good is under 1.8 s.
Speed Index: 8.5 s
8.5 sVisually, the page fills in at 8.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 750 ms
750 msScripts block taps and scrolling for 750 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 281 ms
281 msReal visitors wait 281 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user LCP: 2.2 s
2.2 sReal visitors wait 2.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 788 ms
788 msReal visitors wait 788 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 15% faster for real visitors
-15%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 332 ms to 283 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.0 MB in 160 requests
5.0 MBYour homepage downloads 5.0 MB in 160 requests on a phone: scripts 2.3 MB (65), images 2.1 MB (29) and fonts 317 KiB (9). Under 2 MB keeps phones on slow connections fast.
14 images in older formats
14 images (1.5 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.
6 images below the first screen load straight away
6 images further down the page (582 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.42 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.42 g of CO₂e: 170.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
Links must have discernible text (5 elements)
Links must have discernible text: 5 elements on the page fail this check, rated serious by axe-core.
All page content should be contained by landmarks (6 elements)
All page content should be contained by landmarks: 6 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Alternative text of images should not be repeated as text (5 elements)
Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h6), 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. (3 elements).
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 8 failed. 2 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.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
104 internal links, 25 external
The homepage links to 104 pages on joules.com and 25 external pages.
6 checks passed
Meta description: 78 characters
Your meta description is 78 characters: “Discover our complete range of clothing & footwear at the official Joules site”.
Title: 58 characters
Your title is a healthy 58 characters: “Joules | Women's, Men's & Children's Clothing And Footwear”.
Canonical URL set
The canonical URL is https://www.joules.com/.
Structured data in place
Structured data found: Organization.
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.joules.com/sitemap-index.xml.
AI search readiness
Some text only appears after JavaScript runs
59%The HTML your server sends has 541 of the 922 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.joules.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.
1 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.
Other pages
1 page points its canonical at the homepage
https://www.joules.com/favourites declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
4 pages share 2 titles
/ and https://www.joules.com/favourites all use the title “Joules | Women's, Men's & Children's Clothing And Footwear”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.joules.com/shoppingbag and https://www.joules.com/blog/preppy-takes-the-reins have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://www.joules.com/storelocator, https://www.joules.com/favourites, https://www.joules.com/shoppingbag and https://www.joules.com/blog/preppy-takes-the-reins 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 51 found) and read each the way a search engine does.
3 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 10 pages that loaded have a <title>.
Best practices
112 small tap targets
112 of 132 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 922 words of copy
The homepage carries about 922 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop our latest arrivals”.
7 calls to action
The homepage has 7 calls to action, for example “Register”, “Please try again” and “Start a ChatFor general enquiries”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
21 cookies set on arrival
21Opening the homepage sets 21 cookies (measured from a US location before any click).
16 other companies contacted
Loading the homepage contacts 16 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 joules.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- React
- Analytics
- Google Tag Manager
Company
- Founded
- 1989
- Headquarters
- Market Harborough
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on joules.com, including 20 speed issues, 2 SEO issues and 2 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.