Website review, no card needed
uptherestore.com website review
Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 87 checks
This review found 31 issues worth fixing on uptherestore.com, 10 of them high impact, across 87 checks. The most urgent: render-blocking 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
Site score
87B- #8,377 of 121,919 reviewed websitesbeats 90%
- #4,833 of 68,936 online storesbeats 90%
- #4,682 of 62,814 Shopify storesbeats 89%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.7 s |
| Jun 13, 2026 | 1.7 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.8 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 224 ms |
| Jun 6, 2026 | 219 ms |
| Jun 13, 2026 | 242 ms |
| Jun 20, 2026 | 254 ms |
| Jun 27, 2026 | 270 ms |
| Jul 4, 2026 | 271 ms |
| Jul 11, 2026 | 264 ms |
| Jul 18, 2026 | 260 ms |
| Jul 25, 2026 | 254 ms |
| Aug 1, 2026 | 255 ms |
| Aug 8, 2026 | 261 ms |
| Aug 15, 2026 | 262 ms |
| Aug 22, 2026 | 262 ms |
| Aug 29, 2026 | 261 ms |
| Sep 5, 2026 | 255 ms |
| Sep 12, 2026 | 254 ms |
| Sep 19, 2026 | 254 ms |
| Sep 26, 2026 | 246 ms |
| Oct 3, 2026 | 247 ms |
| Oct 10, 2026 | 248 ms |
| Oct 17, 2026 | 252 ms |
| Oct 24, 2026 | 254 ms |
| Oct 31, 2026 | 246 ms |
| Nov 7, 2026 | 237 ms |
| Nov 14, 2026 | 231 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.9 s
1.8 s
2.7 s
3.6 s
4.5 s
5.4 s
6.3 s
7.3 s
Speed
Render-blocking requests
1.2 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Main-thread work: 11.0 s
A phone's processor spends 11.0 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,778 HTML elements
The page has 3,778 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Improve image delivery
2.0 MB22 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
8 third-party services on the page
8 third-party services load with your homepage (Klaviyo, Stripe and Google Maps and others), adding 1.7 MB and 975 ms of main-thread time.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
825 KiBAbout 825 KiB of JavaScript is downloaded but never used on this page.
Use efficient cache lifetimes
631 KiB16 files are served with short cache lifetimes, so returning visitors download them again (631 KiB).
Klaviyo adds 304 ms
304 msKlaviyo costs a phone 304 ms of main-thread work and 633 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.
Google Maps adds 147 ms
147 msGoogle Maps costs a phone 147 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
150 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
17 long tasks on the main thread
17 long tasks block the main thread while loading, the longest for 193 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
39 KiBPolyfills for old browsers add 39 KiB JavaScript that modern phones do not need.
Minify CSS
7 KiB7 KiB could be saved by minifying CSS.
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: 9 ms
9 msYour server sent the HTML in 9 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 18.8 s
18.8 sThe page becomes fully interactive after 18.8 s. Good is under 3.8 s.
Largest Contentful Paint: 4.5 s
4.5 sYour largest element takes 4.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “image”.
Total Blocking Time: 527 ms
527 msScripts block taps and scrolling for 527 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 224 ms to 231 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, 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).
9 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.2 s
1.2 sReal visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 152 ms
152 msReal visitors wait 152 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.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 407 ms
407 msReal visitors wait 407 ms for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 2.8 s
2.8 sVisually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 211 requests
4.9 MBYour homepage downloads 4.9 MB in 211 requests on a phone: images 2.6 MB (27), scripts 2.0 MB (122) and fonts 171 KiB (4). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
29 KiB1 image is downloaded at several times the size a phone draws it, for example cb99cec0-6744-457e-a4d4-65ff3835c295.gif at 500 px wide, shown at 113 px. Resized copies would save about 29 KiB.
9 images in older formats
9 images (473 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.
About 1.4 g of CO₂ per visit
1.40 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.40 g of CO₂e: 167.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
16 buttons without a name
16 buttons have no accessible name, so screen readers announce just “button”.
19 tap targets too small
19 tap targets are too small or too close together to hit reliably with a finger.
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (53 elements)
All page content should be contained by landmarks: 53 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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 144 images in the HTML carry an alt attribute.
48 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: 48 passed and 6 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 H1 headlines
There are 2 <h1> headlines (“Latest” and “Journal”). One clear main headline is easier for people and search engines.
Structured data has 1 problem
Structured data found (Organization and WebSite) but with 1 problem, for example “WebSite: missing name”.
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.
456 internal links, 8 external
The homepage links to 456 pages on uptherestore.com and 8 external pages.
6 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “Up There Store is a fashion and sneaker boutique based in Melbourne, Australia. 69 Flinders Ln, Melbourne 3000.”.
Title: 57 characters
Your title is a healthy 57 characters: “UP THERE - Australia's Premier Sneaker & Fashion Boutique”.
Canonical URL set
The canonical URL is https://uptherestore.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://uptherestore.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: 5 of 6 facts
Your Organization JSON-LD gives name, url, sameAs (social profiles), description and contact details; logo would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,405 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://uptherestore.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 pages without an H1
https://uptherestore.com/collections/latest, https://uptherestore.com/collections/core, https://uptherestore.com/collections/1733, https://uptherestore.com/collections/19-69, https://uptherestore.com/collections/adidas and https://uptherestore.com/collections/adsum and 9 others 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 194 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.
Every page has a meta description
All 15 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 15 pages that loaded have a <title>.
Best practices
51 small tap targets
51 of 84 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 “Cannot read properties of undefined (reading 'country_name')”.
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.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 477 words of copy
The homepage carries about 477 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “→ SIGN UP”.
6 calls to action
The homepage has 6 calls to action, for example “SHOP ALL”, “→ SHOP ALL BRANDS” and “Sign Up”.
5 short forms
5 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and Klaviyo and 3 mores (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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies, 2 of them by other companies (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.
39 other companies contacted
Loading the homepage contacts 39 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 uptherestore.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Plus
- Hosting
- Shopify
Company
- Headquarters
- Melbourne
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on uptherestore.com, including 13 speed issues, 3 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.