Website review, no card needed

akronchildrens.org logo

akronchildrens.org website review

Visit site (opens in a new tab)Reviewed 18 October 202639 issues · 83 checks

This review found 39 issues worth fixing on akronchildrens.org, 9 of them high impact, across 83 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
2.2 s1.8 sApr 25Oct 102.0 s
Show as table
DateReal-visitor load time (LCP)
Apr 25, 20262.0 s
May 2, 20262.0 s
May 9, 20262.0 s
May 16, 20261.9 s
May 23, 20262.0 s
May 30, 20262.1 s
Jun 6, 20262.1 s
Jun 13, 20262.2 s
Jun 20, 20262.1 s
Jun 27, 20262.1 s
Jul 4, 20262.0 s
Jul 11, 20262.0 s
Jul 18, 20262.0 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.9 s
Aug 15, 20261.9 s
Aug 22, 20261.9 s
Aug 29, 20261.9 s
Sep 5, 20261.9 s
Sep 12, 20261.9 s
Sep 19, 20261.9 s
Sep 26, 20261.9 s
Oct 3, 20261.9 s
Oct 10, 20262.0 s
Real-visitor tap response (INP)75th percentile, phones
77 ms71 msApr 25Oct 1075 ms
Show as table
DateReal-visitor tap response (INP)
Apr 25, 202672 ms
May 2, 202672 ms
May 9, 202672 ms
May 16, 202672 ms
May 23, 202672 ms
May 30, 202673 ms
Jun 6, 202674 ms
Jun 13, 202676 ms
Jun 20, 202675 ms
Jun 27, 202674 ms
Jul 4, 202674 ms
Jul 11, 202673 ms
Jul 18, 202674 ms
Jul 25, 202674 ms
Aug 1, 202674 ms
Aug 8, 202674 ms
Aug 15, 202673 ms
Aug 22, 202673 ms
Aug 29, 202674 ms
Sep 5, 202675 ms
Sep 12, 202676 ms
Sep 19, 202676 ms
Sep 26, 202676 ms
Oct 3, 202675 ms
Oct 10, 202675 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 akronchildrens.org (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. akronchildrens.org at 0.6 s0.6 s
  2. akronchildrens.org at 1.1 s1.1 s
  3. akronchildrens.org at 1.7 s1.7 s
  4. akronchildrens.org at 2.3 s2.3 s
  5. akronchildrens.org at 2.8 s2.8 s
  6. akronchildrens.org at 3.4 s3.4 s
  7. akronchildrens.org at 4.0 s4.0 s
  8. akronchildrens.org at 4.5 s4.5 s

Speed

9 to fix64
  • Render-blocking requests

    2.4 s

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

  • Reduce unused CSS

    1.1 s · 225 KiB

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

  • Reduce unused JavaScript

    900 ms · 224 KiB

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

  • Mobile performance score: 64

    64/100

    Your mobile performance score is 64 (desktop: 71). Pages that score under 90 lose visitors before the first paint.

  • Improve image delivery

    741 KiB

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

  • Minify JavaScript

    600 ms · 86 KiB

    86 KiB could be saved by minifying JavaScript.

  • 8 third-party services on the page

    8 third-party services load with your homepage (jQuery CDN, sitescdn.net and FontAwesome CDN and others), adding 1.1 MB and 523 ms of main-thread time.

  • 1,512 HTML elements

    The page has 1,512 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • FontAwesome CDN adds 117 ms

    117 ms

    FontAwesome CDN costs a phone 117 ms of main-thread work and 333 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.

  • Font display

    200 ms

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

  • 3 long tasks on the main thread

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

  • Use efficient cache lifetimes

    113 KiB

    7 files are served with short cache lifetimes, so returning visitors download them again (113 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.7 s

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

  • Server response: 62 ms

    62 ms

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

Core Web Vitals

6 to fix100
  • Time to Interactive: 11.9 s

    11.9 s

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

  • Largest Contentful Paint: 5.6 s

    5.6 s

    Your largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our providers are always looking for medical advancements a…”.

  • First Contentful Paint: 3.0 s

    3.0 s

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

  • Speed Index: 5.6 s

    5.6 s

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

  • 26 images without width and height

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

  • Cumulative Layout Shift: 0.14

    0.14

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

  • Tap response (INP) held steady for real visitors

    +4%

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

  • Largest content (LCP) held steady for real visitors

    -2%

    Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.0 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.3 s

    1.3 s

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

  • Real-user INP: 59 ms

    59 ms

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

  • Real-user FCP: 1.2 s

    1.2 s

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

  • Real-user TTFB: 469 ms

    469 ms

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

  • Total Blocking Time: 64 ms

    64 ms

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

Images and page weight

4 to fix58
  • Page weight: 2.6 MB in 116 requests

    2.6 MB

    Your homepage downloads 2.6 MB in 116 requests on a phone: images 1.5 MB (55), scripts 492 KiB (17) and fonts 419 KiB (16). Under 2 MB keeps phones on slow connections fast.

  • 14 images in older formats

    14 images (1.1 MB) 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.

  • 9 images below the first screen load straight away

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

  • 3 images far larger than shown

    251 KiB

    3 images are downloaded at several times the size a phone draws them, for example hero-parents.jpg at 2,346 px wide, shown at 390 px. Resized copies would save about 251 KiB.

  • About 0.7 g of CO₂ per visit

    0.75 g

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

Accessibility

7 to fixGoogle 8790
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

  • 1 text element with low contrast

    1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

  • Malformed lists

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

  • 1 tap target too small

    1 tap target is too small or too close together to hit reliably with a finger.

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

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

  • Alternative text of images should not be repeated as text (9 elements)

    Alternative text of images should not be repeated as text: 9 elements on the page fail this check, rated minor by axe-core.

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

    Elements with visible text labels do not have matching accessible names. (1 element).

2 checks passed
  • Every image has alt text

    All 92 images in the HTML carry an alt attribute.

  • 47 automated accessibility rules passed

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

SEO

5 to fixGoogle 9284
  • 7 H1 headlines

    There are 7 <h1> headlines (“For Families & Patients”, “We specialize in onething – kids.” and “Our featured specialties”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (Hospital and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://www.akronchildrens.org/search-answers.html?query=={search_term_s…”.

  • No XML sitemap

    No XML sitemap at https://www.akronchildrens.org/sitemap.xml.gz, so Google discovers your pages only by following links.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 292 internal links, 49 external

    The homepage links to 292 pages on akronchildrens.org and 49 external pages.

5 checks passed
  • Meta description: 103 characters

    Your meta description is 103 characters: “We lead the way to healthier futures for children through quality patient care, education, and advocacy”.

  • Title: 52 characters

    Your title is a healthy 52 characters: “We specialize in one thing – kids : Akron Children's”.

  • Canonical URL set

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

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

AI search readiness

1 to fix88
  • 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.akronchildrens.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.

2 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 (1,710 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 2 pages share a title

    https://www.akronchildrens.org/pages/Ask-Childrens.html and https://www.akronchildrens.org/cgi-bin/mailto_ask-childrens/contact.pl all use the title “Ask Children's | Akron Children's”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 2 pages without a meta description

    https://www.akronchildrens.org/appointments and https://www.akronchildrens.org/search-answers.html have no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.akronchildrens.org/search-answers.html has 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 83 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.

  • Canonical URLs point to themselves

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

  • 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 10087
  • 81 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://assets.sitescdn.net/chat/v0/chat.css' from origin 'https://www.akronchildrens.org'…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix83
  • Thin social proof

    Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

    The homepage carries about 694 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Call the operator at 330-543-1000” and “Contact Us Online”.

  • 16 calls to action

    The homepage has 16 calls to action, for example “Call the operator at 330-543-1000”, “Contact Us Online” and “Gift Shop”.

  • 6 short forms

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

  • Direct contact links

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

Privacy and tracking

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

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

Upkeep, stack and company

Stack

Framework
jQuery

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 39 issues on akronchildrens.org, including 15 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