Website review, no card needed

lansingbp.com logo

lansingbp.com website review

Visit site (opens in a new tab)Reviewed 29 October 202641 issues · 86 checks

This review found 41 issues worth fixing on lansingbp.com, 9 of them high impact, across 86 checks. The most urgent: page weight: 21.8 MB in 117 requests. 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.4 s1.8 sMay 9Oct 242.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20261.9 s
May 30, 20262.0 s
Jun 6, 20262.0 s
Jun 13, 20262.1 s
Jun 20, 20262.2 s
Jun 27, 20262.2 s
Jul 4, 20262.2 s
Jul 11, 20262.2 s
Jul 18, 20262.2 s
Jul 25, 20262.2 s
Aug 1, 20262.1 s
Aug 8, 20262.0 s
Aug 15, 20262.0 s
Aug 22, 20262.0 s
Aug 29, 20262.1 s
Sep 5, 20262.2 s
Sep 12, 20262.2 s
Sep 19, 20262.3 s
Sep 26, 20262.3 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.2 s
Real-visitor tap response (INP)75th percentile, phones
109 ms84 msMay 9Oct 2498 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202696 ms
May 16, 202695 ms
May 23, 202695 ms
May 30, 202697 ms
Jun 6, 2026103 ms
Jun 13, 2026106 ms
Jun 20, 2026106 ms
Jun 27, 202696 ms
Jul 4, 202689 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202692 ms
Aug 1, 202695 ms
Aug 8, 202695 ms
Aug 15, 202695 ms
Aug 22, 202696 ms
Aug 29, 202696 ms
Sep 5, 202697 ms
Sep 12, 202699 ms
Sep 19, 202696 ms
Sep 26, 202697 ms
Oct 3, 202697 ms
Oct 10, 202697 ms
Oct 17, 202699 ms
Oct 24, 202698 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 lansingbp.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

10 to fix73
  • Render-blocking requests

    1.3 s

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

  • Use efficient cache lifetimes

    950 ms · 8.4 MB

    87 files are served with short cache lifetimes, so returning visitors download them again (8.4 MB).

  • Improve image delivery

    5.2 MB

    11 images could be 5.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 73

    73/100

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

  • Reduce unused JavaScript

    805 KiB

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Google Maps and others), adding 1.4 MB and 505 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 33 KiB

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

  • Minify CSS

    300 ms · 10 KiB

    10 KiB could be saved by minifying CSS.

  • Google Tag Manager adds 188 ms

    188 ms

    Google Tag Manager costs a phone 188 ms of main-thread work and 444 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.

  • Google CDN adds 62 ms

    62 ms

    Google CDN costs a phone 62 ms of main-thread work and 352 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.

  • Font display

    200 ms

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

  • 4 long tasks on the main thread

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

  • Legacy JavaScript

    12 KiB

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

2 checks passed
  • Main-thread work: 1.1 s

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

  • Server response: 7 ms

    7 ms

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

Core Web Vitals

7 to fix100
  • 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 s

    Your 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 element shown below.

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Real-user TTFB: 1.2 s

    1.2 s

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

  • 21 images without width and height

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

  • Speed Index: 4.0 s

    4.0 s

    Visually, the page fills in at 4.0 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.

  • Tap response (INP) held steady for real visitors

    +3%

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

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

    +13%

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

6 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 96 ms

    96 ms

    Real visitors wait 96 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.7 s

    1.7 s

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

  • Total Blocking Time: 95 ms

    95 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

5 to fix28
  • Page weight: 21.8 MB in 117 requests

    21.8 MB

    Your homepage downloads 21.8 MB in 117 requests on a phone: images 9.9 MB (47), media 9.9 MB (1) and scripts 1.5 MB (45). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    IMG_1695-e1785958017171.jpeg weighs 604 KiB. On a phone connection a single image that size takes seconds.

  • 3 images in older formats

    3 images (751 KiB) 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.

  • 1 image far larger than shown

    455 KiB

    1 image is downloaded at several times the size a phone draws it, for example IMG_1695-e1785958017171.jpeg at 2,048 px wide, shown at 339 px. Resized copies would save about 455 KiB.

  • 2 images below the first screen load straight away

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

  • About 6.2 g of CO₂ per visit

    6.16 g

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

Accessibility

7 to fixGoogle 8088
  • 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.

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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 (32 elements)

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

  • 7 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • 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 (h3 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 36 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 9290
  • Title is long (70 characters)

    Your title is 70 characters, so Google will cut it off around 60: “Lansing Building Products - Exterior Building Products For Contractors”.

  • No social preview image

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

  • 70 internal links, 33 external

    The homepage links to 70 pages on lansingbp.com and 33 external pages.

6 checks passed
  • Meta description: 133 characters

    Your meta description is 133 characters: “Lansing Building Products supplies exterior building products and materials to professional contractors throughout the …”.

  • One H1 headline

    Your main headline reads: “Delivering excellence from the inside out.”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, Organization, WebPage and WebSite.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://lansingbp.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

  • No llms.txt

    There is no https://lansingbp.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.

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

Other pages

4 to fix81
  • 9 pages share a title

    https://lansingbp.com/product/siding, https://lansingbp.com/product/windows, https://lansingbp.com/product/roofing, https://lansingbp.com/product/gutters, https://lansingbp.com/product/patio and https://lansingbp.com/product/decking-railing and 3 others all use the title “Lansing Building Products”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 1 page without a meta description

    https://lansingbp.com/product/storm-products has no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 pages share a meta description

    https://lansingbp.com/product/siding, https://lansingbp.com/product/windows, https://lansingbp.com/product/roofing, https://lansingbp.com/product/gutters, https://lansingbp.com/product/patio and https://lansingbp.com/product/decking-railing and 3 others use the same meta description. A description written for each page earns more clicks.

  • 9 pages without an H1

    https://lansingbp.com/product/siding, https://lansingbp.com/product/windows, https://lansingbp.com/product/roofing, https://lansingbp.com/product/gutters, https://lansingbp.com/product/patio and https://lansingbp.com/product/decking-railing and 3 others 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 30 found) and read each the way a search engine does.

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

  • 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

2 to fixGoogle 9687
  • 12 small tap targets

    12 of 55 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

2 to fix88
  • 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.

  • Only about 214 words

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

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CONTACT US” and “ORDER ONLINE”.

  • 8 calls to action

    The homepage has 8 calls to action, for example “Contact this Branch »”, “Order Online” and “Contact”.

  • 2 short forms

    2 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 1 testimonial or review block, 2 customer or partner logos, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics and Hotjar.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 12 cookies set on arrival

    12

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

  • 18 other companies contacted

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

Upkeep, stack and company

Stack

CMS
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager | Hotjar
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on lansingbp.com, including 17 speed issues, 2 SEO issues and 2 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