Website review, no card needed

biolagear.com logo

biolagear.com website review

Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 83 checks

This review found 40 issues worth fixing on biolagear.com, 7 of them high impact, across 83 checks. The most urgent: 4,141 HTML elements. 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.0 s675 msMay 23Oct 3988 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026760 ms
May 30, 2026745 ms
Jun 6, 2026732 ms
Jun 13, 2026716 ms
Jul 11, 2026869 ms
Jul 18, 2026854 ms
Jul 25, 2026792 ms
Aug 1, 2026817 ms
Aug 8, 2026868 ms
Aug 15, 2026883 ms
Aug 22, 2026919 ms
Aug 29, 2026933 ms
Sep 5, 2026915 ms
Sep 12, 2026910 ms
Sep 19, 2026967 ms
Oct 3, 2026988 ms
Real-visitor tap response (INP)75th percentile, phones
84 ms60 msMay 23Sep 1279 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202663 ms
May 30, 202663 ms
Jun 6, 202663 ms
Jun 13, 202663 ms
Jul 11, 202666 ms
Jul 18, 202665 ms
Jul 25, 202663 ms
Aug 1, 202663 ms
Aug 8, 202670 ms
Aug 15, 202670 ms
Aug 22, 202679 ms
Aug 29, 202681 ms
Sep 5, 202679 ms
Sep 12, 202679 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 biolagear.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

9 to fix67
  • 4,141 HTML elements

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

  • Mobile performance score: 67

    67/100

    Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    650 ms · 294 KiB

    7 images could be 294 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

  • Render-blocking requests

    850 ms

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

  • Reduce unused JavaScript

    712 KiB

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Hubspot, Google Tag Manager and Shopify and others), adding 1.2 MB and 334 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 72 KiB

    About 72 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Main-thread work: 3.6 s

    A phone's processor spends 3.6 s on main-thread work while loading, 762 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Shopify adds 40 ms

    40 ms

    Shopify costs a phone 40 ms of main-thread work and 875 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.

  • 9 long tasks on the main thread

    9 long tasks block the main thread while loading, the longest for 142 ms. During a long task the page ignores taps.

  • Use efficient cache lifetimes

    138 KiB

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

  • 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: 6 ms

    6 ms

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

Core Web Vitals

6 to fix63
  • Largest Contentful Paint: 8.0 s

    8.0 s

    Your largest element takes 8.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 14.4 s

    14.4 s

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

  • Tap response (INP) got 25% slower for real visitors

    +25%

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

  • Largest content (LCP) got 30% slower for real visitors

    +30%

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

  • Speed Index: 5.3 s

    5.3 s

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

  • Total Blocking Time: 238 ms

    238 ms

    Scripts block taps and scrolling for 238 ms in total while the page loads. Good is under 200 ms.

  • 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
  • First Contentful Paint: 1.2 s

    1.2 s

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

2 to fix75
  • Page weight: 3.5 MB in 286 requests

    3.5 MB

    Your homepage downloads 3.5 MB in 286 requests on a phone: images 1.7 MB (126), scripts 763 KiB (45) and other files 725 KiB (103). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    121 KiB

    1 image is downloaded at several times the size a phone draws it, for example ac.svg at 9,750 px wide, shown at 20 px. Resized copies would save about 121 KiB.

  • 1 image in older formats

    1 image (31 KiB) is 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.

  • 2 images below the first screen load straight away

    2 images further down the page (46 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.99 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.99 g of CO₂e: 118.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

10 to fixGoogle 8489
  • Scrollable region must have keyboard access (3 elements)

    Scrollable region must have keyboard access: 3 elements on the page fail this check, rated serious by axe-core.

  • 11 images without alt text

    11 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (3 elements)

    All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.

  • Contentinfo landmark should not be contained in another landmark (1 element)

    Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one contentinfo landmark (1 element)

    Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • 21 links without text

    21 visible links have no text or label, so screen readers cannot say where they go.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Elements with role="dialog" or role="alertdialog" do not have accessible names.

    Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).

  • Headings skip levels

    Headings skip levels (h3 → h5 and h2 → h4), which makes the page harder to scan with a screen reader.

1 checks passed
  • 43 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: 43 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9273
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “Biola Campus Store | Official Apparel, Gear & Merch – Biola University Campus Store”.

  • Meta description is long (221 characters)

    Your meta description is 221 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.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 190 internal links, 7 external

    The homepage links to 190 pages on biolagear.com and 7 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

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

AI search readiness

100
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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,947 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://biolagear.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix93
  • 15 pages share a meta description

    https://biolagear.com/collections/mens-show-all, https://biolagear.com/collections/mens-tshirts, https://biolagear.com/collections/mens-sweatshirts, https://biolagear.com/collections/mens-tops, https://biolagear.com/collections/mens-bottoms and https://biolagear.com/collections/mens-professional-wear and 9 others use the same meta description. A description written for each page earns more clicks.

  • 15 pages without an H1

    https://biolagear.com/collections/mens-show-all, https://biolagear.com/collections/mens-tshirts, https://biolagear.com/collections/mens-sweatshirts, https://biolagear.com/collections/mens-tops, https://biolagear.com/collections/mens-bottoms and https://biolagear.com/collections/mens-professional-wear and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages slow to respond

    https://biolagear.com/collections/mens-professional-wear and https://biolagear.com/collections/womens-show-all took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

1 to fixGoogle 9693
  • 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 404 ()”.

2 checks passed
  • Tap targets are thumb-sized

    50 of 62 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix67
  • 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.

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

  • Thin social proof

    Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Only about 247 words

    The homepage has only about 247 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop Now”, “Shop Womens” and “Shop Mens”.

  • 55 short forms

    55 short forms (1 field at most) are right on the homepage.

  • 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

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, HubSpot and Meta Pixel (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

  • 20 cookies set on arrival

    20

    Opening the homepage sets 20 cookies, 8 of them by other companies (measured from a US location before any click).

  • 22 other companies contacted

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

1 checks passed
  • Consent tool: HubSpot cookie banner

    A consent management tool (HubSpot cookie banner) 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 biolagear.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 2 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Forms · hubapi.com

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 40 issues on biolagear.com, including 15 speed issues, 5 SEO issues and 5 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