Website review, no card needed
upwind.world website review
Visit site (opens in a new tab)Reviewed 5 November 202635 issues · 74 checks
This review found 35 issues worth fixing on upwind.world, 8 of them high impact, across 74 checks. The most urgent: hidden but focusable. 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- #49,772 of 97,881 reviewed websitesbeats 44%
- #31,423 of 53,367 online storesbeats 36%
- #29,945 of 48,397 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Aug 15, 2026 | 876 ms |
| Aug 22, 2026 | 897 ms |
| Aug 29, 2026 | 909 ms |
| Sep 5, 2026 | 909 ms |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 1.0 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Aug 15, 2026 | 85 ms |
| Aug 22, 2026 | 84 ms |
| Aug 29, 2026 | 85 ms |
| Sep 5, 2026 | 86 ms |
| Sep 12, 2026 | 94 ms |
| Sep 19, 2026 | 102 ms |
| Sep 26, 2026 | 105 ms |
| Oct 3, 2026 | 109 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Improve image delivery
700 ms · 573 KiB16 images could be 573 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Mobile performance score: 69
69/100Your mobile performance score is 69. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 93 KiB6 files are served with short cache lifetimes, so returning visitors download them again (93 KiB).
Reduce unused CSS
450 ms · 65 KiBAbout 65 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.
Render-blocking requests
500 ms5 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
Reduce unused JavaScript
440 ms · 45 KiBAbout 45 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 440 ms faster on a phone.
2,046 HTML elements
The page has 2,046 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
150 ms · 14 KiBPolyfills for old browsers add 14 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (adoric-om.com, Shopify and useamp.com and others), adding 228 KiB and 53 ms of main-thread time.
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
2 KiB2 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 290 ms of it running JavaScript. That is comfortably low.
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 8.7 s
8.7 sYour largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 8.8 s
8.8 sThe page becomes fully interactive after 8.8 s. Good is under 3.8 s.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 85 ms to 109 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 0.9 s to 1.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Speed Index: 5.5 s
5.5 sVisually, the page fills in at 5.5 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.0 s
2.0 sThe first text or image appears after 2.0 s on a phone. Good is under 1.8 s.
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
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
Page weight: 3.1 MB in 250 requests
3.1 MBYour homepage downloads 3.1 MB in 250 requests on a phone: images 1.6 MB (33), other files 895 KiB (127) and scripts 403 KiB (82). Under 2 MB keeps phones on slow connections fast.
6 images below the first screen load straight away
6 images further down the page (245 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.9 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
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “Unique Sustainable brand using scrap materials to design garments – Upwind.World”.
Meta description is long (263 characters)
Your meta description is 263 characters; Google truncates after about 160, so the end of your pitch is cut.
84 internal links, 7 external
The homepage links to 84 pages on upwind.world and 7 external pages.
6 checks passed
One H1 headline
Your main headline reads: “Upcycled jackets and bags made from recycled kitesurfing sails”.
Canonical URL set
The canonical URL is https://www.upwind.world/.
Structured data in place
Structured data found: Organization and WebSite.
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.upwind.world/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), 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.
3 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 (716 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.upwind.world/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://www.upwind.world/pages/shop-menu is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages share a title
https://www.upwind.world/products/mistral and https://www.upwind.world/products/mistral-white all use the title “Mistral Jacket – Upwind.World”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.upwind.world/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.upwind.world/products/mistral and https://www.upwind.world/products/mistral-white use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.upwind.world/pages/jacket-menu and https://www.upwind.world/pages/shop-menu 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 35 found) and read each the way a search engine does.
3 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 401 ()”.
2 checks passed
Tap targets are thumb-sized
19 of 19 tappable elements near the top are at least 24 px.
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.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 351 words of copy
The homepage carries about 351 words of visible text.
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Shop”, “Contact Us” and “Contact information”.
18 short forms
18 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Microsoft Clarity (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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
11 other companies contacted
Loading the homepage contacts 11 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 upwind.world, 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 5 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Back In Stock · nfcube.com · adoric-om.com · getmason.io · cloudfront.net
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
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on upwind.world, including 13 speed issues, 2 SEO issues and 6 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.