Website review, no card needed

bksteppers.org logo

bksteppers.org website review

Visit site (opens in a new tab)Reviewed 6 November 202632 issues · 95 checks

This review found 32 issues worth fixing on bksteppers.org, 8 of them high impact, across 95 checks. The most urgent: page weight: 7.5 MB in 56 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

Live view · interaction off

Speed

6 to fix92
  • 8 third-party services on the page

    8 third-party services load with your homepage (Facebook, Google Tag Manager and leadconnectorhq.com and others), adding 7.4 MB and 429 ms of main-thread time.

  • Render-blocking requests

    700 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

  • filesafe.space adds 0 ms

    0 ms

    filesafe.space costs a phone 0 ms of main-thread work and 6.6 MB 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.

  • Reduce unused JavaScript

    314 KiB

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

  • Improve image delivery

    262 KiB

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

  • leadconnectorhq.com adds 11 ms

    11 ms

    leadconnectorhq.com costs a phone 11 ms of main-thread work and 373 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

    240 KiB

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

  • 8 long tasks on the main thread

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

  • Legacy JavaScript

    23 KiB

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

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

  • Minify CSS

    2 KiB

    2 KiB could be saved by minifying CSS.

3 checks passed
  • Mobile performance score: 92

    92/100

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

  • Main-thread work: 1.6 s

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

  • Server response: 5 ms

    5 ms

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

Core Web Vitals

4 to fix92
  • Time to Interactive: 10.4 s

    10.4 s

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

  • Total Blocking Time: 292 ms

    292 ms

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • 3 images without width and height

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

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

3 checks passed
  • Largest Contentful Paint: 1.8 s

    1.8 s

    Your largest element renders in 1.8 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “In New York City, a young person can fall in love with drum…”.

  • Cumulative Layout Shift: 0.008

    0.008

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

  • Speed Index: 1.8 s

    1.8 s

    Visually, the page fills in at 1.8 s (Speed Index), inside the 3.4 s “good” threshold.

Images and page weight

5 to fix18
  • Page weight: 7.5 MB in 56 requests

    7.5 MB

    Your homepage downloads 7.5 MB in 56 requests on a phone: images 6.6 MB (10), scripts 809 KiB (28) and HTML 47 KiB (1). Under 2 MB keeps phones on slow connections fast.

  • 3 images over 500 KB

    3 images weigh 5.8 MB together. On a phone connection a single image that size takes seconds.

  • 6 images far larger than shown

    5.5 MB

    6 images are downloaded at several times the size a phone draws them, for example 6a90528b60935b340b68a480.jpg at 4,240 px wide, shown at 306 px. Resized copies would save about 5.5 MB.

  • 6 images in older formats

    6 images (6.5 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.

  • 5 images below the first screen load straight away

    5 images further down the page (6.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.1 g of CO₂ per visit

    2.12 g

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

Accessibility

1 to fixGoogle 9899
  • All page content should be contained by landmarks (22 elements)

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 36 automated accessibility rules passed

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

SEO

3 to fixGoogle 10089
  • No structured data

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

  • No canonical URL

    No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

  • No social preview image

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

  • No X (Twitter) card tag

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

  • 27 internal links, 8 external

    The homepage links to 27 pages on bksteppers.org and 8 external pages.

5 checks passed
  • Meta description: 151 characters

    Your meta description is 151 characters: “BK Steppers is a 37-year cultural institution developing young marching percussionists in Brooklyn, Mount Vernon, and o…”.

  • One H1 headline

    Your main headline reads: “Keep a kid on the drumline.”.

  • Title: 57 characters

    Your title is a healthy 57 characters: “Brooklyn Steppers | Drumline & Marching Percussion in NYC”.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.bksteppers.org/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.

  • No llms.txt

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

Other pages

2 to fix90
  • 7 pages share 2 titles

    /about, /give and /schools all use the title “Give to Brooklyn Steppers | Sustain the Marching Arts Pathway”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 7 pages share a meta description

    /about, /give and /schools use the same meta description. A description written for each page earns more clicks.

  • 9 internal pages checked

    We fetched 9 pages linked from your homepage and read each the way a search engine does.

6 checks passed
  • Linked pages load

    All 9 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 9 pages that loaded have a meta description.

  • 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 9 pages that loaded have a <title>.

Best practices

Google 100100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Security and trust

3 to fix71
  • 1 broken link to your own pages

    1 link from your homepage to your own site is broken, for example https://www.bksteppers.org/cdn-cgi/l/email-protection (404).

  • No HSTS header

    No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

  • No Content-Security-Policy

    No Content-Security-Policy header, the main browser-side defence against injected scripts.

  • No clickjacking protection

    Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

  • No X-Content-Type-Options

    X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

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

  • No security.txt

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

4 checks passed
  • Served over HTTPS

    The homepage is served over HTTPS (bksteppers.org).

  • Valid certificate (77 days left)

    The certificate from Google Trust Services · WE1 verifies for bksteppers.org and is valid for another 77 days.

  • http:// redirects to https

    http://bksteppers.org redirects to the secure version.

  • HTTP/2

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

Domain and trust

1 to fix
  • Domain expires in 67 days

    bksteppers.org is registered until Jan 2027. Make sure auto-renew is on and the card on file is current.

  • No CAA record

    bksteppers.org 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

    bksteppers.org'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.

1 checks passed
  • Domain is 16 years old

    16 years

    bksteppers.org was registered in Jan 2010 through eNom, LLC. An established domain carries more trust with email providers and search engines.

Content and conversion

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

  • No opening hours

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 1,470 words of copy

    The homepage carries about 1,470 words of visible text.

5 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Contact” and “Start your free lesson →”.

  • Social proof on the page

    Social proof on the homepage: 2 testimonial or review blocks and “350+ Students”.

  • Analytics in place

    Analytics detected: Meta Pixel and Cloudflare Web Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 0 email links.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

Email authentication

3 to fix0
  • No DMARC policy

    bksteppers.org has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

  • No SPF record

    bksteppers.org has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

  • No DKIM key on the usual selectors

    We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

  • Email authentication score: 0/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.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

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

  • 4 cookies set on arrival

    4

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

  • 15 other companies contacted

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

Upkeep, stack and company

No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.

Stack

Framework
Nuxt
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on bksteppers.org, including 10 speed issues, 3 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