Website review, no card needed
theharvardshop.com website review
Visit site (opens in a new tab)Reviewed 6 November 202633 issues · 79 checks
This review found 33 issues worth fixing on theharvardshop.com, 8 of them high impact, across 79 checks. The most urgent: page weight: 15.3 MB in 401 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
80B- #48,341 of 124,112 reviewed websitesbeats 55%
- #31,945 of 69,786 online storesbeats 48%
- #30,694 of 63,472 Shopify storesbeats 45%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.5 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.6 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.4 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 146 ms |
| May 23, 2026 | 142 ms |
| May 30, 2026 | 141 ms |
| Jun 6, 2026 | 142 ms |
| Jun 13, 2026 | 144 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 166 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 186 ms |
| Jul 18, 2026 | 187 ms |
| Jul 25, 2026 | 187 ms |
| Aug 1, 2026 | 185 ms |
| Aug 8, 2026 | 182 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 171 ms |
| Aug 29, 2026 | 171 ms |
| Sep 5, 2026 | 174 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 186 ms |
| Sep 26, 2026 | 188 ms |
| Oct 3, 2026 | 185 ms |
| Oct 10, 2026 | 178 ms |
| Oct 17, 2026 | 174 ms |
| Oct 24, 2026 | 176 ms |
| Oct 31, 2026 | 174 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.8 s
1.7 s
2.5 s
3.3 s
4.2 s
5.0 s
5.8 s
6.7 s
Speed
Reduce unused JavaScript
770 ms · 473 KiBAbout 473 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 770 ms faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and Privy and others), adding 1.4 MB and 572 ms of main-thread time.
Improve image delivery
410 KiB6 images could be 410 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Shopify adds 256 ms
256 msShopify costs a phone 256 ms of main-thread work and 682 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.
Main-thread work: 2.8 s
A phone's processor spends 2.8 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,836 HTML elements
The page has 1,836 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 108 ms
108 msKlaviyo costs a phone 108 ms of main-thread work and 327 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.
Use efficient cache lifetimes
150 ms · 115 KiB14 files are served with short cache lifetimes, so returning visitors download them again (115 KiB).
Reduce unused CSS
150 ms · 60 KiBAbout 60 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.
Legacy JavaScript
19 KiBPolyfills for old browsers add 19 KiB JavaScript that modern phones do not need.
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
5 KiB5 KiB could be saved by minifying JavaScript.
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
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: 6.5 s
6.5 sYour largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies on our website to provide the best browsing …”.
Time to Interactive: 14.1 s
14.1 sThe page becomes fully interactive after 14.1 s. Good is under 3.8 s.
Speed Index: 6.9 s
6.9 sVisually, the page fills in at 6.9 s (Speed Index). Good is under 3.4 s.
Real-user INP: 208 ms
208 msReal visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 22% slower for real visitors
+22%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 146 ms to 174 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.5 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 695 ms
695 msReal visitors wait 695 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.002
0.002The layout barely moves while loading (CLS 0.002, good is under 0.1).
Total Blocking Time: 50 ms
50 msScripts block the page for only 50 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 15.3 MB in 401 requests
15.3 MBYour homepage downloads 15.3 MB in 401 requests on a phone: media 10.9 MB (3), images 1.6 MB (23) and scripts 1.5 MB (193). Under 2 MB keeps phones on slow connections fast.
8 images far larger than shown
309 KiB8 images are downloaded at several times the size a phone draws them, for example quincy-01.jpg at 900 px wide, shown at 252 px. Resized copies would save about 309 KiB.
About 4.3 g of CO₂ per visit
4.35 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.35 g of CO₂e: 521.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 load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
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.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), 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. (2 elements).
1 checks passed
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (225 characters)
Your meta description is 225 characters; Google truncates after about 160, so the end of your pitch is cut.
101 internal links, 86 external
The homepage links to 101 pages on theharvardshop.com and 86 external pages.
7 checks passed
One H1 headline
Your main headline reads: “The Harvard Shop”.
Title: 62 characters
Your title is a healthy 62 characters: “The Harvard Shop - Harvard's Official Student-Run Campus Store”.
Canonical URL set
The canonical URL is https://www.theharvardshop.com/.
Structured data in place
Structured data found: Organization.
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.theharvardshop.com/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 (877 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.theharvardshop.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a meta description
https://www.theharvardshop.com/collections/hats-ties/CURRENT has no meta description, so Google writes the search snippet from whatever text it finds.
14 pages share a meta description
https://www.theharvardshop.com/collections/new-arrivals/CURRENT, https://www.theharvardshop.com/collections/bestsellers/CURRENT, https://www.theharvardshop.com/collections/student-favorites/CURRENT, https://www.theharvardshop.com/collections/premium-items/CURRENT, https://www.theharvardshop.com/collections/t-shirts-2/CURRENT and https://www.theharvardshop.com/collections/mens-sweaters-and-sweatshirts/CURRENT and 8 others use the same meta description. A description written for each page earns more clicks.
15 links to non-canonical URLs
Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.theharvardshop.com/collections/new-arrivals/CURRENT, whose canonical is https://www.theharvardshop.com/collections/new-arrivals/current. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 54 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
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
5 small tap targets
5 of 23 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 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 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.
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 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 448 words of copy
The homepage carries about 448 words of visible text.
2 checks passed
15 calls to action
The homepage has 15 calls to action, for example “Made to Order”, “Clothing Shop now” and “Accessories Shop now”.
1 short form
A short form (1 field at most) is right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and Klaviyo (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.
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.
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 theharvardshop.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 6 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Aris Product Options · Yotpo Product Reviews · Klaviyo Email Marketing Sms · spinasale.com · privy.com · good-apps.co
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
- Framework
- jQuery
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Headquarters
- Cambridge
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on theharvardshop.com, including 15 speed issues, 1 SEO issue and 4 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.