Website review, no card needed

twincitiespainclinic.com logo

twincitiespainclinic.com website review

Visit site (opens in a new tab)Reviewed 24 October 202632 issues · 86 checks

This review found 32 issues worth fixing on twincitiespainclinic.com, 13 of them high impact, across 86 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.9 s2.3 sMay 2Oct 172.8 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20262.4 s
May 9, 20262.4 s
May 16, 20262.5 s
May 23, 20262.5 s
May 30, 20262.5 s
Jun 6, 20262.6 s
Jun 13, 20262.5 s
Jun 20, 20262.6 s
Jun 27, 20262.5 s
Jul 4, 20262.5 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.6 s
Aug 1, 20262.6 s
Aug 8, 20262.5 s
Aug 15, 20262.6 s
Aug 22, 20262.6 s
Aug 29, 20262.7 s
Sep 5, 20262.7 s
Sep 12, 20262.7 s
Sep 19, 20262.6 s
Sep 26, 20262.6 s
Oct 3, 20262.7 s
Oct 10, 20262.6 s
Oct 17, 20262.8 s
Real-visitor tap response (INP)75th percentile, phones
110 ms93 msMay 2Oct 17101 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026103 ms
May 9, 2026103 ms
May 16, 2026105 ms
May 23, 2026106 ms
May 30, 2026101 ms
Jun 6, 2026101 ms
Jun 13, 202697 ms
Jun 20, 202695 ms
Jun 27, 202697 ms
Jul 4, 2026100 ms
Jul 11, 2026104 ms
Jul 18, 2026108 ms
Jul 25, 2026105 ms
Aug 1, 2026100 ms
Aug 8, 202696 ms
Aug 15, 202697 ms
Aug 22, 202698 ms
Aug 29, 2026101 ms
Sep 5, 2026105 ms
Sep 12, 2026106 ms
Sep 19, 2026105 ms
Sep 26, 2026106 ms
Oct 3, 2026104 ms
Oct 10, 202697 ms
Oct 17, 2026101 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 twincitiespainclinic.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

11 to fix39
  • Reduce unused JavaScript

    3.5 s · 699 KiB

    About 699 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.

  • Use efficient cache lifetimes

    2.7 s · 468 KiB

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

  • Render-blocking requests

    3.1 s

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

  • Reduce unused CSS

    1.4 s · 173 KiB

    About 173 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.

  • Mobile performance score: 39

    39/100

    Your mobile performance score is 39 (desktop: 69). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google CDN, Google Maps and Accessibe Accessibility Overlay and others), adding 1.4 MB and 1.2 s of main-thread time.

  • Improve image delivery

    800 ms · 128 KiB

    1 image could be 128 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.

  • Main-thread work: 3.1 s

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

  • Google CDN adds 272 ms

    272 ms

    Google CDN costs a phone 272 ms of main-thread work and 351 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 Maps adds 264 ms

    264 ms

    Google Maps costs a phone 264 ms of main-thread work and 391 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.

  • 10 long tasks on the main thread

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

  • Minify CSS

    150 ms · 9 KiB

    9 KiB could be saved by minifying CSS.

  • Legacy JavaScript

    50 ms · 8 KiB

    Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

  • Phones get a much slower page than desktops

    Desktop scores 69 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • 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: 14 ms

    14 ms

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

Core Web Vitals

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

  • First Contentful Paint: 8.4 s

    8.4 s

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

  • Largest Contentful Paint: 17.0 s

    17.0 s

    Your largest element takes 17.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Minnesota’s Pain Management Experts Visit Twin Cities Pain …”.

  • Time to Interactive: 17.0 s

    17.0 s

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

  • Speed Index: 8.4 s

    8.4 s

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

  • Real-user CLS: 0.15

    0.15

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

  • Total Blocking Time: 586 ms

    586 ms

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

  • Cumulative Layout Shift: 0.1

    0.1

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

  • 2 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -4%

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

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

    +14%

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

4 checks passed
  • Real-user LCP: 2.4 s

    2.4 s

    Real visitors wait 2.4 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 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: 788 ms

    788 ms

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 120 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 120 requests on a phone: scripts 1.5 MB (45), images 788 KiB (36) and fonts 214 KiB (3). Under 2 MB keeps phones on slow connections fast.

  • 1 image in older formats

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

  • 3 images below the first screen load straight away

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

  • About 0.8 g of CO₂ per visit

    0.78 g

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

1 checks passed
  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9092
  • 9 text elements with low contrast

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

  • 6 images without alt text

    6 images have no alt text, which hurts accessibility and image search.

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

    All page content should be contained by landmarks: 9 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.

  • 5 links without text

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

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

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

SEO

1 to fixGoogle 9298
  • 6 links with vague text

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

  • 125 internal links, 4 external

    The homepage links to 125 pages on twincitiespainclinic.com and 4 external pages.

8 checks passed
  • Meta description: 138 characters

    Your meta description is 138 characters: “Feel Better, Move Better, Live Better. Find lasting relief from chronic pain with the help of our board certified pain …”.

  • One H1 headline

    Your main headline reads: “Minnesota’s Pain Management Experts”.

  • Title: 61 characters

    Your title is a healthy 61 characters: “Twin Cities Pain Clinic | Minnesota's Pain Management Experts”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, ImageObject, Organization, WebPage 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://twincitiespainclinic.com/sitemap_index.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.

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.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://twincitiespainclinic.com/llms.txt (9 KiB, 71 links, though it should open with a “# Title” line), a plain-text guide to the site for AI tools.

Other pages

100
  • 15 internal pages checked

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

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

  • Every page has a meta description

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

Best practices

2 to fixGoogle 9291
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “t(...).ut_require_js is not a function”.

  • 1 distorted image

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

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix79
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a map 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 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 471 words of copy

    The homepage carries about 471 words of visible text.

5 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Schedule an Appointment”.

  • 14 calls to action

    The homepage has 14 calls to action, for example “Contact Us”, “Schedule an Appointment” and “Schedule Online”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

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

  • Phone number on the homepage

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

Privacy and tracking

  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Termly) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: Termly

    A consent management tool (Termly) loads with the page.

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

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 twincitiespainclinic.com, including 20 speed issues, 1 SEO issue 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
twincitiespainclinic.com website review: scores and fixes