Website review, no card needed

ubookstore.com logo

ubookstore.com website review

Visit site (opens in a new tab)Reviewed 9 November 202621 issues · 100 checks

This review found 21 issues worth fixing on ubookstore.com, 0 of them high impact, across 100 checks. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.1 s889 msMay 23Nov 7913 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 2026970 ms
Jun 13, 2026979 ms
Jun 20, 2026971 ms
Jun 27, 2026952 ms
Jul 4, 2026994 ms
Jul 11, 20261.0 s
Jul 18, 20261.0 s
Jul 25, 20261.1 s
Aug 1, 20261.0 s
Aug 8, 20261.0 s
Aug 15, 2026980 ms
Aug 22, 2026935 ms
Aug 29, 2026942 ms
Sep 5, 2026934 ms
Sep 12, 2026945 ms
Sep 19, 2026958 ms
Sep 26, 2026953 ms
Oct 3, 2026951 ms
Oct 10, 2026953 ms
Oct 17, 2026956 ms
Oct 24, 2026962 ms
Oct 31, 2026959 ms
Nov 7, 2026913 ms
Real-visitor tap response (INP)75th percentile, phones
121 ms67 msMay 23Nov 7105 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202673 ms
May 30, 202677 ms
Jun 6, 202678 ms
Jun 13, 202679 ms
Jun 20, 202679 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202679 ms
Jul 18, 202679 ms
Jul 25, 202680 ms
Aug 1, 202680 ms
Aug 8, 202683 ms
Aug 15, 202681 ms
Aug 22, 202679 ms
Aug 29, 202682 ms
Sep 5, 202685 ms
Sep 12, 202688 ms
Sep 19, 202689 ms
Sep 26, 202688 ms
Oct 3, 202691 ms
Oct 10, 202695 ms
Oct 17, 2026100 ms
Oct 24, 2026112 ms
Oct 31, 2026115 ms
Nov 7, 2026105 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

Full-page screenshot of ubookstore.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ubookstore.com at 0.4 s0.4 s
  2. ubookstore.com at 0.8 s0.8 s
  3. ubookstore.com at 1.1 s1.1 s
  4. ubookstore.com at 1.5 s1.5 s
  5. ubookstore.com at 1.9 s1.9 s
  6. ubookstore.com at 2.3 s2.3 s
  7. ubookstore.com at 2.6 s2.6 s
  8. ubookstore.com at 3.0 s3.0 s

ubookstore.com does not allow embedding, so this is Google's rendering of the page.

Speed

4 to fix97
  • Render-blocking requests

    650 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 650 ms.

  • Improve image delivery

    448 KiB

    9 images could be 448 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2,265 HTML elements

    The page has 2,265 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Klaviyo adds 118 ms

    118 ms

    Klaviyo costs a phone 118 ms of main-thread work and 419 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.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Klaviyo, Clarity and Shopify and others), adding 632 KiB and 248 ms of main-thread time.

  • Reduce unused JavaScript

    176 KiB

    About 176 KiB of JavaScript is downloaded but never used on this page.

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 62 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    57 KiB

    About 57 KiB of CSS is downloaded but never applied on this page.

  • Use efficient cache lifetimes

    19 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).

  • Legacy JavaScript

    19 KiB

    Polyfills for old browsers add 19 KiB JavaScript that modern phones do not need.

  • Minify CSS

    6 KiB

    6 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.

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

3 checks passed
  • Mobile performance score: 97

    97/100

    Your mobile performance score is 97. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

    A phone's processor spends 1.1 s on main-thread work while loading, 551 ms of it running JavaScript. That is comfortably low.

  • Server response: 6 ms

    6 ms

    Your server sent the HTML in 6 ms, well inside Google's 600 ms guideline.

Core Web Vitals

3 to fix100
  • Tap response (INP) got 47% slower for real visitors

    +47%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 73 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 4.1 s

    4.1 s

    Visually, the page fills in at 4.1 s (Speed Index). Good is under 3.4 s.

  • Time to Interactive: 4.0 s

    4.0 s

    The page becomes fully interactive after 4.0 s. Good is under 3.8 s.

11 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 s

    Real visitors wait 1.2 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 128 ms

    128 ms

    Real visitors wait 128 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.9 s

    0.9 s

    Real visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 499 ms

    499 ms

    Real visitors wait 499 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 12% faster for real visitors

    -12%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.1 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0.082

    0.082

    The layout barely moves while loading (CLS 0.082, good is under 0.1).

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.1 s

    1.1 s

    Your largest element renders in 1.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “SPEND $99 OR MORE AND GET FREE SHIPPING.”.

  • Total Blocking Time: 6 ms

    6 ms

    Scripts block the page for only 6 ms while loading. Good is under 200 ms.

Images and page weight

3 to fix68
  • Page weight: 3.0 MB in 225 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 225 requests on a phone: images 1.2 MB (27), other files 838 KiB (113) and scripts 777 KiB (76). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (1.4 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 (543 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.84 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.84 g of CO₂e: 100.9 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 to fixGoogle 10099
  • 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.

  • 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 68 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 1 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10088
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is long (185 characters)

    Your meta description is 185 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 542 internal links, 17 external

    The homepage links to 542 pages on ubookstore.com and 17 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “University Book Store”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “University Book Store: University of Washington Bookstore”.

  • Canonical URL set

    The canonical URL is https://ubookstore.com/.

  • 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://ubookstore.com/sitemap.xml.

AI search readiness

1 to fix88
  • No Organization structured data

    There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

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 (1,335 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes /llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

1 to fix95
  • 4 pages without a meta description

    /pages/day-one-access, /pages/va-third-party-funded-students, /collections/textbooks-other-categories and /collections/study-aids-reference have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 200 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.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    16 of 17 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

100
  • Short HSTS lifetime

    HSTS is set, but max-age is 91 days; one year is the recommended minimum.

  • No Referrer-Policy

    No Referrer-Policy header, so full URLs can leak to the sites you link to.

  • No Permissions-Policy

    No Permissions-Policy header to switch off camera, microphone and location for embedded content.

  • Deprecated X-XSS-Protection

    X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

  • No security.txt

    There is no /.well-known/security.txt telling researchers how to report a security problem to you.

7 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (ubookstore.com).

  • Valid certificate (76 days left)

    The certificate from Let's Encrypt · YE1 verifies for ubookstore.com and is valid for another 76 days.

  • Protected from clickjacking

    X-Frame-Options or a frame-ancestors policy stops other sites framing yours.

  • Content-Security-Policy set

    A Content-Security-Policy is set, the main browser-side defence against injected scripts.

  • http:// redirects to https

    http://ubookstore.com redirects to the secure version.

  • HTTP/2 and HTTP/3

    The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.

  • All 51 links work

    All 51 links checked from your homepage (40 internal, 11 external) answered without errors.

Domain and trust

  • No CAA record

    ubookstore.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

  • DNSSEC is off

    ubookstore.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

2 checks passed
  • Domain is 29 years old

    29 years

    ubookstore.com was registered in Sep 1997 through Cloudflare, Inc.. An established domain carries more trust with email providers and search engines.

  • Registered until Jun 2032

    ubookstore.com is registered until Jun 2032.

Content and conversion

4 to fix78
  • 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.

  • 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.

  • Thin social proof

    Social proof on the homepage: 12 customer or partner logos. 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 340 words of copy

    The homepage carries about 340 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP COLLECTION”.

  • 33 calls to action

    The homepage has 33 calls to action, for example “Order Your Materials”, “Shop by UW School” and “Shop by Brand”.

  • 2 short forms

    2 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.

Email authentication

85
  • Email authentication score: 85/100

    Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

3 checks passed
  • DMARC policy: quarantine

    DMARC tells receivers to quarantine mail that fails authentication, and sends you reports.

  • SPF in place (~all)

    An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 mx ip4:66.175.56.0/24 ip4:66.175.57.0/24 ip4:66.175.22.0/24 include:spf.protection.outlook.com include:shops.sho…”.

  • DKIM signing found

    A DKIM key is published (selector “selector1”), so receivers can verify mail really came from you.

Privacy and tracking

1 to fix
  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 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.

  • 23 other companies contacted

    Loading the homepage contacts 23 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

Apps on your store

Your storefront loads 5 apps. Each one is code from another company running for your shoppers.

None of the apps your storefront loads is on the list of apps with a known security problem.

Apps your storefront loads

Klaviyo Email Marketing Sms · Microsoft Clarity · Judge Me Reviews · Regios Discounts · nice-team.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
Analytics
Microsoft Clarity
Hosting
Shopify

Company

Employees
67
Founded
1900
Headquarters
Seattle

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on ubookstore.com, including 7 speed issues, 3 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25