Website review, no card needed

cedarlanelabs.com logo

cedarlanelabs.com website review

Visit site (opens in a new tab)Reviewed 24 October 202637 issues · 93 checks

This review found 37 issues worth fixing on cedarlanelabs.com, 12 of them high impact, across 93 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
2.1 s1.1 sMay 2Oct 171.6 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20261.5 s
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.5 s
May 30, 20261.7 s
Jun 6, 20261.6 s
Jun 13, 20261.8 s
Jun 20, 20261.9 s
Jun 27, 20261.9 s
Jul 4, 20262.0 s
Jul 11, 20261.8 s
Jul 18, 20261.8 s
Jul 25, 20261.6 s
Aug 1, 20261.6 s
Aug 8, 20261.5 s
Aug 15, 20261.5 s
Aug 22, 20261.5 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.4 s
Sep 26, 20261.5 s
Oct 3, 20261.5 s
Oct 10, 20261.7 s
Oct 17, 20261.6 s
Real-visitor tap response (INP)75th percentile, phones
179 ms67 msMay 2Oct 17166 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 202685 ms
May 9, 202682 ms
May 16, 202680 ms
May 23, 202680 ms
May 30, 202687 ms
Jun 6, 202684 ms
Jun 13, 202687 ms
Jun 20, 202689 ms
Jun 27, 202683 ms
Jul 4, 202689 ms
Jul 11, 202685 ms
Jul 18, 2026100 ms
Jul 25, 2026101 ms
Aug 1, 202691 ms
Aug 8, 2026100 ms
Aug 15, 202687 ms
Aug 22, 202697 ms
Aug 29, 2026109 ms
Sep 5, 2026105 ms
Sep 12, 2026100 ms
Sep 19, 202684 ms
Sep 26, 202684 ms
Oct 3, 202690 ms
Oct 10, 2026136 ms
Oct 17, 2026166 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 cedarlanelabs.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

6 to fix52
  • Reduce unused JavaScript

    7.4 s · 1.1 MB

    About 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.4 s faster on a phone.

  • Avoid multiple page redirects

    5.3 s

    The page goes through 2 redirects before it starts loading, costing about 5.3 s. Link and advertise the final URL directly.

  • Render-blocking requests

    1.9 s

    14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.9 s.

  • Main-thread work: 4.5 s

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

  • Mobile performance score: 52

    52/100

    Your mobile performance score is 52 (desktop: 8). Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 0 ms

    0 ms

    Google Tag Manager costs a phone 0 ms of main-thread work and 331 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 · 84 KiB

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Other Google APIs/SDKs, Google Analytics and Google Fonts and others), adding 535 KiB and 178 ms of main-thread time.

  • 20 long tasks on the main thread

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

  • Minify JavaScript

    150 ms · 27 KiB

    27 KiB could be saved by minifying JavaScript.

  • Font display

    100 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).

  • Legacy JavaScript

    18 KiB

    Polyfills for old browsers add 18 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.

1 checks passed
  • Server response: 2 ms

    2 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 15.1 s

    15.1 s

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

  • Time to Interactive: 20.5 s

    20.5 s

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

  • First Contentful Paint: 3.9 s

    3.9 s

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

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

    +81%

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

  • Total Blocking Time: 495 ms

    495 ms

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Largest content (LCP) held steady for real visitors

    +3%

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

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

    1.4 s

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

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

    1.3 s

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

  • Real-user TTFB: 676 ms

    676 ms

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

  • Cumulative Layout Shift: 0.018

    0.018

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

Images and page weight

1 to fix85
  • Page weight: 3.0 MB in 173 requests

    3.0 MB

    Your homepage downloads 3.0 MB in 173 requests on a phone: scripts 2.6 MB (95), stylesheets 162 KiB (26) and fonts 100 KiB (4). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.85 g

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

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

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

12 to fixGoogle 7683
  • 1 button without a name

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

  • 6 text elements with low contrast

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

  • 2 tap targets too small

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

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

  • 7 form fields without a label

    7 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 3 links without text

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 19 images in the HTML carry an alt attribute.

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

SEO

4 to fixGoogle 9283
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “High Quality Antibody Research Lab & Reagent Manufacturing - Cedarlane”.

  • Meta description is long (273 characters)

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 124 internal links, 4 external

    The homepage links to 124 pages on cedarlanelabs.com and 4 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “PROUDLY OFFERING HIGH QUALITY RESEARCH & DIAGNOSTIC ANTIBODIES, KITS, CHEMICALS, AND REAGENTS!”.

  • Canonical URL set

    The canonical URL is https://www.cedarlanelabs.com/.

  • Structured data in place

    Structured data found: LocalBusiness and Organization.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.cedarlanelabs.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Organization data: 4 of 6 facts

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

  • Text is in the HTML

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

Other pages

3 to fix88
  • 4 pages share a meta description

    https://www.cedarlanelabs.com/About, https://www.cedarlanelabs.com/Services/Sales, https://www.cedarlanelabs.com/CustomServices and https://www.cedarlanelabs.com/Newlab use the same meta description. A description written for each page earns more clicks.

  • 13 links to non-canonical URLs

    Your homepage links to 13 pages by a URL that isn't their canonical one, for example https://www.cedarlanelabs.com/About, whose canonical is https://www.cedarlanelabs.com/about. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    https://www.cedarlanelabs.com/Services/Sales, https://www.cedarlanelabs.com/CustomServices and https://www.cedarlanelabs.com/Newlab 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 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.

  • Every page has a meta description

    All 14 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 14 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7388
  • 22 small tap targets

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

  • Deprecated browser APIs

    The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 distorted image

    1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

  • 2 low-resolution images

    2 images are served at too low a resolution for sharp phone screens.

2 checks passed
  • No console errors

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • Thin social proof

    Social proof on the homepage: 21 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

  • About 405 words of copy

    The homepage carries about 405 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Register” and “SHOP BY CATEGORY”.

  • 13 calls to action

    The homepage has 13 calls to action, for example “Register”, “Request a Quote” and “Shop By Category”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • 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
  • 3 trackers load before any consent

    3

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

  • 18 cookies set on arrival

    18

    Opening the homepage sets 18 cookies, 4 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.

  • 17 other companies contacted

    Loading the homepage contacts 17 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 cedarlanelabs.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Bootstrap
Analytics
Google Analytics | Google Tag Manager

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on cedarlanelabs.com, including 12 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