Website review, no card needed

granditasca.org logo

granditasca.org website review

Visit site (opens in a new tab)Reviewed 29 October 202634 issues · 82 checks

This review found 34 issues worth fixing on granditasca.org, 13 of them high impact, across 82 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
876 ms733 msMay 9Oct 24791 ms
Show as table
DateReal-visitor load time (LCP)
May 9, 2026770 ms
May 16, 2026767 ms
May 23, 2026797 ms
May 30, 2026826 ms
Jun 6, 2026859 ms
Jun 13, 2026808 ms
Jun 20, 2026799 ms
Jun 27, 2026820 ms
Jul 4, 2026812 ms
Jul 11, 2026839 ms
Jul 18, 2026827 ms
Jul 25, 2026783 ms
Aug 1, 2026758 ms
Aug 8, 2026752 ms
Aug 15, 2026749 ms
Aug 22, 2026762 ms
Aug 29, 2026762 ms
Sep 5, 2026761 ms
Sep 12, 2026753 ms
Sep 19, 2026757 ms
Sep 26, 2026762 ms
Oct 3, 2026772 ms
Oct 10, 2026795 ms
Oct 17, 2026785 ms
Oct 24, 2026791 ms
Real-visitor tap response (INP)75th percentile, phones
98 ms81 msMay 9Oct 2488 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202685 ms
May 16, 202686 ms
May 23, 202688 ms
May 30, 202695 ms
Jun 6, 202696 ms
Jun 13, 202695 ms
Jun 20, 202695 ms
Jun 27, 202694 ms
Jul 4, 202694 ms
Jul 11, 202694 ms
Jul 18, 202691 ms
Jul 25, 202687 ms
Aug 1, 202687 ms
Aug 8, 202685 ms
Aug 15, 202685 ms
Aug 22, 202687 ms
Aug 29, 202686 ms
Sep 5, 202688 ms
Sep 12, 202687 ms
Sep 19, 202687 ms
Sep 26, 202687 ms
Oct 3, 202683 ms
Oct 10, 202687 ms
Oct 17, 202687 ms
Oct 24, 202688 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 granditasca.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. granditasca.org at 0.5 s0.5 s
  2. granditasca.org at 0.9 s0.9 s
  3. granditasca.org at 1.4 s1.4 s
  4. granditasca.org at 1.8 s1.8 s
  5. granditasca.org at 2.3 s2.3 s
  6. granditasca.org at 2.7 s2.7 s
  7. granditasca.org at 3.2 s3.2 s
  8. granditasca.org at 3.6 s3.6 s

Speed

5 to fix49
  • Reduce unused JavaScript

    2.9 s · 546 KiB

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

  • Render-blocking requests

    2.3 s

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

  • Mobile performance score: 49

    49/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Google Tag Manager, Pinterest and StackAdapt and others), adding 1.1 MB and 800 ms of main-thread time.

  • Google Tag Manager adds 739 ms

    739 ms

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

  • Improve image delivery

    150 ms · 22 KiB

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

  • Reduce unused CSS

    150 ms · 17 KiB

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

  • 8 long tasks on the main thread

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

  • Use efficient cache lifetimes

    15 KiB

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

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

2 checks passed
  • Main-thread work: 1.3 s

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

  • Server response: 4 ms

    4 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.7 s

    14.7 s

    Your largest element takes 14.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A healthcare provider in an OR setting”.

  • First Contentful Paint: 5.3 s

    5.3 s

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

  • Time to Interactive: 14.7 s

    14.7 s

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

  • Speed Index: 6.2 s

    6.2 s

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

  • Total Blocking Time: 451 ms

    451 ms

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

  • 1 image without width and height

    1 image 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-10-24, real Chrome visitors' tap response (inp) went from 85 ms to 88 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Largest content (LCP) held steady for real visitors

    +3%

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

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

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

  • Real-user INP: 92 ms

    92 ms

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

  • Real-user CLS: 0.04

    0.04

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

  • Real-user FCP: 0.9 s

    0.9 s

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

  • Real-user TTFB: 464 ms

    464 ms

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

  • Cumulative Layout Shift: 0.033

    0.033

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

Images and page weight

1 to fix97
  • An image on the first screen is lazy-loaded

    KatyJohnson_web2.avif is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.5 g of CO₂ per visit

    0.50 g

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

3 checks passed
  • Page weight: 1.8 MB in 53 requests

    1.8 MB

    Your homepage downloads 1.8 MB in 53 requests on a phone: scripts 1.2 MB (17), fonts 448 KiB (5) and images 40 KiB (5). That is a lean page.

  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

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

Accessibility

8 to fixGoogle 9291
  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • Banner landmark should not be contained in another landmark (1 element)

    Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Document should not have more than one banner landmark (1 element)

    Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

  • Page should contain a level-one heading (1 element)

    Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

2 checks passed
  • Every image has alt text

    All 3 images in the HTML carry an alt attribute.

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

SEO

5 to fixGoogle 8572
  • No meta description

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

  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • No structured data

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

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 2 links with vague text

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

  • No X (Twitter) card tag

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

  • 59 internal links, 9 external

    The homepage links to 59 pages on granditasca.org and 9 external pages.

4 checks passed
  • Title: 41 characters

    Your title is a healthy 41 characters: “Homepage | Grand Itasca Clinic & Hospital”.

  • Canonical URL set

    The canonical URL is https://www.granditasca.org/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.granditasca.org/sitemap.xml.

AI search readiness

2 to fix53
  • robots.txt blocks 2 AI answer engine crawlers

    2 of 6

    Your robots.txt shuts out ChatGPT (ChatGPT-User) and Perplexity (PerplexityBot). These fetch pages to answer people's questions and cite the source, so your site can't be quoted or linked in those answers.

  • 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 https://www.granditasca.org/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.

  • Opted out of AI training for 3 crawlers

    robots.txt blocks GPTBot, ClaudeBot and Google-Extended, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers.

1 checks passed
  • Text is in the HTML

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

Other pages

3 to fix85
  • 15 pages without a meta description

    https://www.granditasca.org/get-care, https://www.granditasca.org/providers, https://www.granditasca.org/locations, https://www.granditasca.org/pay-a-bill, https://www.granditasca.org/specialties-and-services and https://www.granditasca.org/careers and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 link to non-canonical URLs

    Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.granditasca.org/locations, whose canonical is https://www.granditasca.org/locations/list. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 7 pages without an H1

    https://www.granditasca.org/providers, https://www.granditasca.org/locations, https://www.granditasca.org/pay-a-bill, https://www.granditasca.org/blog, https://www.granditasca.org/contact-us and https://www.granditasca.org/media and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

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

4 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

  • 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

1 to fixGoogle 10093
  • 16 small tap targets

    16 of 21 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

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

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

    The homepage carries about 361 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Contact Us 24/7”, “Learn More” 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.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 8 cookies set on arrival

    8

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

  • 12 other companies contacted

    Loading the homepage contacts 12 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 granditasca.org, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

CMS
Drupal
Framework
jQuery
Analytics
Google Tag Manager
Hosting
Fastly

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on granditasca.org, including 11 speed issues, 5 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