Website review, no card needed

mblawfirm.com logo

mblawfirm.com website review

Visit site (opens in a new tab)Reviewed 2 November 202621 issues · 75 checks

This review found 21 issues worth fixing on mblawfirm.com, 8 of them high impact, across 75 checks. The most urgent: render-blocking 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
3.6 s2.5 sMay 16Oct 313.5 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20262.7 s
May 23, 20262.7 s
May 30, 20262.6 s
Jun 6, 20262.7 s
Jun 13, 20262.8 s
Jun 20, 20262.9 s
Jun 27, 20263.0 s
Jul 4, 20262.9 s
Jul 11, 20262.9 s
Jul 18, 20262.8 s
Jul 25, 20262.8 s
Aug 1, 20262.9 s
Aug 8, 20262.9 s
Aug 15, 20263.0 s
Aug 22, 20263.1 s
Aug 29, 20263.1 s
Sep 5, 20263.2 s
Sep 12, 20263.3 s
Sep 19, 20263.4 s
Sep 26, 20263.5 s
Oct 3, 20263.5 s
Oct 10, 20263.4 s
Oct 17, 20263.4 s
Oct 24, 20263.4 s
Oct 31, 20263.5 s
Real-visitor tap response (INP)75th percentile, phones
86 ms70 msMay 16Oct 3177 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202676 ms
May 23, 202676 ms
May 30, 202673 ms
Jun 6, 202672 ms
Jun 13, 202677 ms
Jun 20, 202674 ms
Jun 27, 202679 ms
Jul 4, 202679 ms
Jul 11, 202678 ms
Jul 18, 202675 ms
Jul 25, 202673 ms
Aug 1, 202673 ms
Aug 8, 202676 ms
Aug 15, 202680 ms
Aug 22, 202684 ms
Aug 29, 202682 ms
Sep 5, 202679 ms
Sep 12, 202679 ms
Sep 19, 202676 ms
Sep 26, 202675 ms
Oct 3, 202678 ms
Oct 10, 202678 ms
Oct 17, 202678 ms
Oct 24, 202678 ms
Oct 31, 202677 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 mblawfirm.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

5 to fix71
  • Render-blocking requests

    3.3 s

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

  • Improve image delivery

    1.4 s · 543 KiB

    3 images could be 543 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.4 s faster on a phone.

  • Use efficient cache lifetimes

    1.3 s · 422 KiB

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

  • Mobile performance score: 71

    71/100

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

  • Reduce unused CSS

    750 ms · 100 KiB

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

  • 4 third-party services on the page

    4 third-party services load with your homepage (GoDaddy, Google Fonts and Adobe TypeKit and others), adding 188 KiB and 37 ms of main-thread time.

  • 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: 0.4 s

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

  • Server response: 98 ms

    98 ms

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

Core Web Vitals

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

    6.3 s

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

  • First Contentful Paint: 3.3 s

    3.3 s

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

  • Real-user LCP: 2.5 s

    2.5 s

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

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

    +28%

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Time to Interactive: 6.3 s

    6.3 s

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

  • Tap response (INP) held steady for real visitors

    +2%

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

5 checks passed
  • Real-user INP: 82 ms

    82 ms

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

  • Speed Index: 3.3 s

    3.3 s

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

  • Cumulative Layout Shift: 0.027

    0.027

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

  • Total Blocking Time: 0 ms

    0 ms

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

Images and page weight

1 to fix90
  • 1 image far larger than shown

    28 KiB

    1 image is downloaded at several times the size a phone draws it, for example MBLogo-Sunset1A-White.png at 1,500 px wide, shown at 354 px. Resized copies would save about 28 KiB.

  • 1 image in older formats

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

  • About 0.3 g of CO₂ per visit

    0.35 g

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

2 checks passed
  • Page weight: 1.2 MB in 52 requests

    1.2 MB

    Your homepage downloads 1.2 MB in 52 requests on a phone: images 757 KiB (5), fonts 198 KiB (4) and stylesheets 154 KiB (34). That is a lean page.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

Accessibility

3 to fixGoogle 9396
  • 19 text elements with low contrast

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

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

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

  • 25 links without text

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

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (2 elements).

2 checks passed
  • Every image has alt text

    All 15 images in the HTML carry an alt attribute.

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

SEO

1 to fixGoogle 10095
  • Meta description is long (162 characters)

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

  • 169 internal links, 20 external

    The homepage links to 169 pages on mblawfirm.com and 20 external pages.

7 checks passed
  • One H1 headline

    Your main headline reads: “Mandelbaum Barrett PC”.

  • Title: 45 characters

    Your title is a healthy 45 characters: “Full Service Law Firm | Mandelbaum Barrett PC”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LegalService and WebSite.

  • 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://mblawfirm.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://mblawfirm.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: 5 of 6 facts

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

  • Text is in the HTML

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

Other pages

100
  • 5 pages slow to respond

    https://mblawfirm.com/our-promise-to-you, https://mblawfirm.com/about-us/success-stories, https://mblawfirm.com/reviews, https://mblawfirm.com/practice-areas/bankruptcy-and-creditors-rights and https://mblawfirm.com/practice-areas/cannabis-hemp-psychedelics took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 74 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

    12 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 12 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

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

Best practices

2 to fixGoogle 10078
  • 1 broken image

    1 image failed to load on a phone, for example https://mblawfirm.com/.

  • 5 small tap targets

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

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 fix95
  • Thin social proof

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

  • About 536 words of copy

    The homepage carries about 536 words of visible text.

9 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “CALL US NOW”.

  • 5 calls to action

    The homepage has 5 calls to action, for example “Contact”, “Learn More About Our Team” and “Contact Us”.

  • 2 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and HubSpot.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

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

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

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 cookies set on arrival

    3

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

  • 6 other companies contacted

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

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 mblawfirm.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 | Microsoft Clarity
Hosting
Sucuri

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 21 issues on mblawfirm.com, including 13 speed issues, 1 SEO issue 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