Website review, no card needed

becausesciencedc.com logo

becausesciencedc.com website review

Visit site (opens in a new tab)Reviewed 8 November 202638 issues · 90 checks

This review found 38 issues worth fixing on becausesciencedc.com, 11 of them high impact, across 90 checks. The most urgent: reduce unused JavaScript. 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.7 s1.4 sMay 16Oct 311.4 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.5 s
Jun 13, 20261.4 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.4 s
Jul 18, 20261.5 s
Jul 25, 20261.5 s
Aug 1, 20261.4 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.6 s
Sep 12, 20261.7 s
Sep 19, 20261.6 s
Sep 26, 20261.6 s
Oct 3, 20261.6 s
Oct 10, 20261.6 s
Oct 17, 20261.5 s
Oct 24, 20261.5 s
Oct 31, 20261.4 s
Real-visitor tap response (INP)75th percentile, phones
111 ms86 msMay 16Oct 3196 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202694 ms
May 23, 202689 ms
May 30, 202694 ms
Jun 6, 202695 ms
Jun 13, 202695 ms
Jun 20, 202696 ms
Jun 27, 202695 ms
Jul 4, 202696 ms
Jul 11, 202696 ms
Jul 18, 202696 ms
Jul 25, 202696 ms
Aug 1, 202693 ms
Aug 8, 202691 ms
Aug 15, 202690 ms
Aug 22, 202699 ms
Aug 29, 202698 ms
Sep 5, 2026102 ms
Sep 12, 2026104 ms
Sep 19, 202699 ms
Sep 26, 2026104 ms
Oct 3, 2026108 ms
Oct 10, 2026108 ms
Oct 17, 2026108 ms
Oct 24, 2026104 ms
Oct 31, 202696 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 becausesciencedc.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. becausesciencedc.com at 0.8 s0.8 s
  2. becausesciencedc.com at 1.6 s1.6 s
  3. becausesciencedc.com at 2.4 s2.4 s
  4. becausesciencedc.com at 3.2 s3.2 s
  5. becausesciencedc.com at 4.0 s4.0 s
  6. becausesciencedc.com at 4.8 s4.8 s
  7. becausesciencedc.com at 5.6 s5.6 s
  8. becausesciencedc.com at 6.4 s6.4 s

Speed

13 to fix62
  • Reduce unused JavaScript

    3.6 s · 588 KiB

    About 588 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.6 s faster on a phone.

  • Main-thread work: 4.9 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Klaviyo and JSDelivr CDN and others), adding 2.4 MB and 1.1 s of main-thread time.

  • Mobile performance score: 62

    62/100

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

  • Use efficient cache lifetimes

    600 ms · 173 KiB

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

  • Shopify adds 708 ms

    708 ms

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

  • Improve image delivery

    400 ms · 299 KiB

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

  • Legacy JavaScript

    350 ms · 69 KiB

    Polyfills for old browsers add 69 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 350 ms faster on a phone.

  • Reduce unused CSS

    300 ms · 44 KiB

    About 44 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.

  • 2,828 HTML elements

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

  • Klaviyo adds 178 ms

    178 ms

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

  • cloudfront.net adds 40 ms

    40 ms

    cloudfront.net costs a phone 40 ms of main-thread work and 901 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.

  • Amazon Web Services adds 43 ms

    43 ms

    Amazon Web Services costs a phone 43 ms of main-thread work and 299 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.

  • Render-blocking requests

    150 ms

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

  • 6 long tasks on the main thread

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

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 21.5 s

    21.5 s

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

  • Time to Interactive: 21.8 s

    21.8 s

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

  • Speed Index: 8.7 s

    8.7 s

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

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

  • 12 images without width and height

    12 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    +9%

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

  • Largest content (LCP) held steady for real visitors

    0%

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

8 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: 2.1 s

    2.1 s

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

  • Real-user INP: 124 ms

    124 ms

    Real visitors wait 124 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: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 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.

  • Total Blocking Time: 195 ms

    195 ms

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

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

3 to fix45
  • Page weight: 4.4 MB in 349 requests

    4.4 MB

    Your homepage downloads 4.4 MB in 349 requests on a phone: images 1.7 MB (43), scripts 1.6 MB (155) and other files 868 KiB (129). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    9875ed6e-14d0-4521-bd7b-0d209e4fb6a0.png weighs 829 KiB. On a phone connection a single image that size takes seconds.

  • 1 image in older formats

    1 image (829 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.

  • 1 image below the first screen load straight away

    1 image further down the page (23 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.3 g of CO₂ per visit

    1.26 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.26 g of CO₂e: 150.7 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

6 to fixGoogle 8992
  • 144 tap targets too small

    144 tap targets are too small or too close together to hit reliably with a finger.

  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • Hidden but focusable

    3 elements hidden from screen readers can still receive keyboard focus.

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

  • 9 links without text

    9 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 (1 element)

    Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

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

SEO

4 to fixGoogle 9282
  • Title is short (15 characters)

    Your title is only 15 characters: “Because Science”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (268 characters)

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

  • Structured data has 3 problems

    Structured data found (Store, WebPage and WebSite) but with 3 problems, for example “Store: logo is not an absolute URL ("//becausesciencedc.com/cdn/shop/files/1_because_science_atom_a…”.

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

  • 484 internal links, 10 external

    The homepage links to 484 pages on becausesciencedc.com and 10 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Because Science”.

  • Canonical URL set

    The canonical URL is https://becausesciencedc.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://becausesciencedc.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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 2 pages without a meta description

    https://becausesciencedc.com/collections/magnets and https://becausesciencedc.com/collections/mugs have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://becausesciencedc.com/collections/stickers has 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 108 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.

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

  • 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

3 to fixGoogle 9671
  • 6 broken images

    6 images failed to load on a phone, for example https://becausesciencedc.com/.

  • 98 small tap targets

    98 of 152 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 400 ()”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • No analytics detected

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

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

    The homepage carries about 931 words of visible text.

  • Urgency cues

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

7 checks passed
  • Clear next step on the first screen

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

  • 18 calls to action

    The homepage has 18 calls to action, for example “SHOP ALL”, “Contact” and “Shop science gifts”.

  • 4 short forms

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

  • Social proof on the page

    Social proof on the homepage: 67 testimonial or review blocks, a star rating and 1 trust badge.

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 48 other companies contacted

    Loading the homepage contacts 48 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 becausesciencedc.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 16 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Blockify Fraud Filter · Judge Me Reviews · Upload Lift · Klaviyo Email Marketing Sms · Also Bought · Inbox · Region Restrictions · Automatic Discounts Upsells · chimpstatic.com · scopemedia.com · hulkapps.com · mailerlite.com · cloudfront.net · nfcube.com · amazonaws.com · roseperl.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

Framework
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Hiring

Hiring
1 open role
Job board
careers page

Company

Headquarters
Washington

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 38 issues on becausesciencedc.com, including 18 speed issues, 4 SEO issues and 1 conversion gap. 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