Website review, no card needed

Dr. Jose Barrera, MD Plastic Surgery and MedSpa logo

drjosebarrera.com website review

Visit site (opens in a new tab)Reviewed 16 November 202629 issues · 83 checks

This review found 29 issues worth fixing on drjosebarrera.com, 4 of them high impact, across 83 checks. The most urgent: page weight: 26.2 MB in 82 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

Read the full growth playbook for Dr. Jose Barrera, MD Plastic Surgery and MedSpa

  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.0 s1.5 sMay 30Nov 141.9 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20261.8 s
Jun 6, 20261.8 s
Jun 13, 20261.8 s
Jun 20, 20261.7 s
Jun 27, 20261.7 s
Jul 4, 20261.7 s
Jul 11, 20261.7 s
Jul 18, 20261.7 s
Jul 25, 20261.7 s
Aug 1, 20261.7 s
Aug 8, 20261.6 s
Aug 15, 20261.6 s
Aug 22, 20261.6 s
Aug 29, 20261.6 s
Sep 5, 20261.8 s
Sep 12, 20261.7 s
Sep 19, 20261.7 s
Sep 26, 20261.7 s
Oct 3, 20261.7 s
Oct 10, 20261.8 s
Oct 17, 20261.8 s
Oct 24, 20261.8 s
Oct 31, 20261.9 s
Nov 7, 20261.9 s
Nov 14, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
82 ms59 msMay 30Nov 1479 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 202678 ms
Jun 6, 202674 ms
Jun 13, 202673 ms
Jun 20, 202672 ms
Jun 27, 202673 ms
Jul 4, 202673 ms
Jul 11, 202671 ms
Jul 18, 202671 ms
Jul 25, 202671 ms
Aug 1, 202670 ms
Aug 8, 202666 ms
Aug 15, 202663 ms
Aug 22, 202663 ms
Aug 29, 202669 ms
Sep 5, 202673 ms
Sep 12, 202671 ms
Sep 19, 202670 ms
Sep 26, 202663 ms
Oct 3, 202662 ms
Oct 10, 202662 ms
Oct 17, 202670 ms
Oct 24, 202671 ms
Oct 31, 202671 ms
Nov 7, 202676 ms
Nov 14, 202679 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 drjosebarrera.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

7 to fix89
  • Mobile performance score: 89

    89/100

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

  • Render-blocking requests

    850 ms

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google Tag Manager, Facebook and userway.org and others), adding 687 KiB and 522 ms of main-thread time.

  • Reduce unused CSS

    300 ms · 63 KiB

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

  • Google Tag Manager adds 271 ms

    271 ms

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

    277 KiB

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

  • Main-thread work: 2.1 s

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

  • Reduce unused JavaScript

    249 KiB

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

  • 6 long tasks on the main thread

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

  • Use efficient cache lifetimes

    160 KiB

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

  • Legacy JavaScript

    53 KiB

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

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 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.

  • Time to Interactive: 9.5 s

    9.5 s

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

  • Real-user CLS: 0.16

    0.16

    For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.8 s

    1.8 s

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

  • Real-user TTFB: 1.7 s

    1.7 s

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

  • Total Blocking Time: 278 ms

    278 ms

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

  • Cumulative Layout Shift: 0.123

    0.123

    The layout shifts by 0.123 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • 6 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    +7%

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

5 checks passed
  • Real-user LCP: 1.9 s

    1.9 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Speed Index: 3.2 s

    3.2 s

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

  • First Contentful Paint: 1.4 s

    1.4 s

    The first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.

  • Largest Contentful Paint: 1.4 s

    1.4 s

    Your largest element renders in 1.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Dr. Jose Barrera is a master of transformation. His greates…”.

Images and page weight

1 to fix70
  • Page weight: 26.2 MB in 82 requests

    26.2 MB

    Your homepage downloads 26.2 MB in 82 requests on a phone: media 24.3 MB (2), scripts 735 KiB (33) and images 612 KiB (15). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

    1 image (69 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 7.4 g of CO₂ per visit

    7.43 g

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

2 checks passed
  • 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

4 to fixGoogle 9496
  • 34 text elements with low contrast

    34 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 (16 elements)

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

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

  • 30 links without text

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

2 checks passed
  • Every image has alt text

    All 54 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 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 8584
  • Title is long (74 characters)

    Your title is 74 characters, so Google will cut it off around 60: “San Antonio, TX Facial Plastic & Reconstructive Surgery | Dr. Jose Barrera”.

  • 10 links with vague text

    10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 9 links crawlers can't follow

    9 links have no real href, so search engines can't follow them.

  • One H1 headline

    Your <h1> is empty.

  • 186 internal links, 25 external

    The homepage links to 186 pages on drjosebarrera.com and 25 external pages.

6 checks passed
  • Meta description: 153 characters

    Your meta description is 153 characters: “Dr. Jose Barrera is a triple board-certified surgeon specializing in cosmetic and reconstructive surgery of the face, n…”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, LocalBusiness, Physician and VideoObject.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://drjosebarrera.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

1 to fix95
  • 1 page without a meta description

    https://drjosebarrera.com/about-us/speaking-events has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://drjosebarrera.com/about-us/patient-stories-and-reviews, https://drjosebarrera.com/resources/in-the-media and https://drjosebarrera.com/plastic-surgery-faqs took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • 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 8891
  • 3 JavaScript errors while loading

    3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix95
  • A 12-field form

    Your longest form asks for 12 fields (7 required). Every extra field lowers completion.

  • About 1,292 words of copy

    The homepage carries about 1,292 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: “Pricing” and “Contact”.

  • 15 calls to action

    The homepage has 15 calls to action, for example “Pricing”, “Contact” and “Shop”.

  • Social proof on the page

    Social proof on the homepage: 12 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 6 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

1 to fix
  • 3 trackers load before any consent

    3

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

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

  • 8 other companies contacted

    Loading the homepage contacts 8 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 drjosebarrera.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 Tag Manager
Hosting
K Media Tech Ltd.

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 29 issues on drjosebarrera.com, including 15 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