Website review, no card needed

gfclinic.com logo

gfclinic.com website review

Visit site (opens in a new tab)Reviewed 29 October 202642 issues · 90 checks

This review found 42 issues worth fixing on gfclinic.com, 21 of them high impact, across 90 checks. The most urgent: improve image delivery. 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.8 s2.1 sMay 9Oct 242.4 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.5 s
May 16, 20262.5 s
May 23, 20262.4 s
May 30, 20262.4 s
Jun 6, 20262.5 s
Jun 13, 20262.6 s
Jun 20, 20262.7 s
Jun 27, 20262.6 s
Jul 4, 20262.6 s
Jul 11, 20262.6 s
Jul 18, 20262.6 s
Jul 25, 20262.7 s
Aug 1, 20262.7 s
Aug 8, 20262.7 s
Aug 15, 20262.7 s
Aug 22, 20262.7 s
Aug 29, 20262.6 s
Sep 5, 20262.6 s
Sep 12, 20262.6 s
Sep 19, 20262.5 s
Sep 26, 20262.4 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.4 s
Real-visitor tap response (INP)75th percentile, phones
120 ms92 msMay 9Oct 24113 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202695 ms
May 16, 2026101 ms
May 23, 2026103 ms
May 30, 2026103 ms
Jun 6, 2026106 ms
Jun 13, 2026104 ms
Jun 20, 2026104 ms
Jun 27, 2026105 ms
Jul 4, 2026103 ms
Jul 11, 2026101 ms
Jul 18, 2026100 ms
Jul 25, 202698 ms
Aug 1, 2026103 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026107 ms
Aug 29, 2026112 ms
Sep 5, 2026114 ms
Sep 12, 2026113 ms
Sep 19, 2026114 ms
Sep 26, 2026113 ms
Oct 3, 2026113 ms
Oct 10, 2026117 ms
Oct 17, 2026113 ms
Oct 24, 2026113 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 gfclinic.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. gfclinic.com at 1.2 s1.2 s
  2. gfclinic.com at 2.4 s2.4 s
  3. gfclinic.com at 3.7 s3.7 s
  4. gfclinic.com at 4.9 s4.9 s
  5. gfclinic.com at 6.1 s6.1 s
  6. gfclinic.com at 7.3 s7.3 s
  7. gfclinic.com at 8.5 s8.5 s
  8. gfclinic.com at 9.8 s9.8 s

Speed

12 to fix29
  • Improve image delivery

    5.1 s · 2.8 MB

    6 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.1 s faster on a phone.

  • Use efficient cache lifetimes

    3.5 s · 1.9 MB

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

  • Render-blocking requests

    4.2 s

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

  • Google Tag Manager adds 1.4 s

    1.4 s

    Google Tag Manager costs a phone 1.4 s of main-thread work and 1.2 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Reduce unused CSS

    1.1 s · 206 KiB

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

  • Mobile performance score: 29

    29/100

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

  • Main-thread work: 6.7 s

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, rlets.com and Google Maps and others), adding 2.0 MB and 2.9 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 940 KiB

    About 940 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • rlets.com adds 627 ms

    627 ms

    rlets.com costs a phone 627 ms of main-thread work and 51 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.

  • 20 long tasks on the main thread

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

  • Google Maps adds 426 ms

    426 ms

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

  • Minify CSS

    150 ms · 40 KiB

    40 KiB could be saved by minifying CSS.

  • Font display

    100 ms

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

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

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

    7 ms

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

Core Web Vitals

10 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: 13.4 s

    13.4 s

    Your largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “ORTHOPEDIC CENTER Great Falls Hospital is an award-winning …”. Most of its time is resource load delay (6.2 s).

  • Time to Interactive: 30.3 s

    30.3 s

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

  • Speed Index: 14.8 s

    14.8 s

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

  • Total Blocking Time: 2.1 s

    2.1 s

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

  • First Contentful Paint: 4.6 s

    4.6 s

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

  • Real-user LCP: 3.0 s

    3.0 s

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

  • Real-user FCP: 2.4 s

    2.4 s

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

  • Real-user TTFB: 1.6 s

    1.6 s

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

  • 4 images without width and height

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

  • Tap response (INP) got 15% slower for real visitors

    +15%

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

  • Largest content (LCP) held steady for real visitors

    -8%

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

3 checks passed
  • Real-user INP: 95 ms

    95 ms

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

  • Cumulative Layout Shift: 0.037

    0.037

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

Images and page weight

2 to fix63
  • Page weight: 6.5 MB in 149 requests

    6.5 MB

    Your homepage downloads 6.5 MB in 149 requests on a phone: images 3.7 MB (16), scripts 2.2 MB (67) and stylesheets 304 KiB (46). Under 2 MB keeps phones on slow connections fast.

  • 2 images below the first screen load straight away

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

  • 3 images in older formats

    3 images (370 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.

  • About 1.8 g of CO₂ per visit

    1.84 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.84 g of CO₂e: 220.8 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 8693
  • Certain ARIA roles must contain particular children (18 elements)

    Certain ARIA roles must contain particular children: 18 elements on the page fail this check, rated critical by axe-core.

  • 45 text elements with low contrast

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

  • Frames without titles

    1 frame has no title, so screen-reader users cannot tell what it contains.

  • ARIA role should be appropriate for the element (21 elements)

    ARIA role should be appropriate for the element: 21 elements on the page fail this check, rated minor by axe-core.

  • 3 links without text

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

  • Headings skip levels

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

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

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

2 checks passed
  • Every image has alt text

    All 9 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 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 6 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 9278
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is short (29 characters)

    Your title is only 29 characters: “Homepage | Great Falls Clinic”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 4 H1 headlines

    There are 4 <h1> headlines (“Orthopedic Center”, “Cardiac Care” and “Pulmonary”). One clear main headline is easier for people and search engines.

  • 58 internal links, 14 external

    The homepage links to 58 pages on gfclinic.com and 14 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://gfclinic.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://gfclinic.com/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

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

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

  • Text is in the HTML

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

Other pages

2 to fix90
  • 1 page without a meta description

    https://gfclinic.com/outreach has no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages without an H1

    https://gfclinic.com/locations, https://gfclinic.com/the-bee-award and https://gfclinic.com/the-daisy-award have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages slow to respond

    https://gfclinic.com/online-bill-pay, https://gfclinic.com/contact-us, https://gfclinic.com/patient-portal, https://gfclinic.com/providers, https://gfclinic.com/outreach and https://gfclinic.com/departments and 9 others took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

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

  • Titles are unique

    Every page we checked has its own title.

  • 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

4 to fixGoogle 7770
  • 1 broken image

    1 image failed to load on a phone, for example https://jelly.mdhv.io/v1/star.gif?pid=jAWxHnVzD7pgcIHvR6gPsGJWGEtk&src=mh&evt=hi.

  • 9 third-party cookies

    9 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

  • 7 small tap targets

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_TUNNEL_CONNECTION_FAILED”.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix72
  • 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.

  • 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 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 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 606 words of copy

    The homepage carries about 606 words of visible text.

6 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Schedule an Appointment”, “Contact Us” and “Patient Pricing Information”.

  • 2 short forms

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

  • Analytics in place

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

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 10 cookies set on arrival

    10

    Opening the homepage sets 10 cookies, 1 of them by other companies (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.

  • 26 other companies contacted

    Loading the homepage contacts 26 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 gfclinic.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

Company

Founded
1917

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 42 issues on gfclinic.com, including 22 speed issues, 3 SEO issues and 3 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