Website review, no card needed

amikids.org logo

amikids.org website review

Visit site (opens in a new tab)Reviewed 31 October 202643 issues · 90 checks

This review found 43 issues worth fixing on amikids.org, 18 of them high impact, across 90 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
3.6 s1.9 sMay 9Oct 242.3 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20262.1 s
May 16, 20262.3 s
May 23, 20262.6 s
May 30, 20262.8 s
Jun 6, 20263.0 s
Jun 13, 20263.0 s
Jun 20, 20263.1 s
Jun 27, 20263.0 s
Jul 4, 20263.1 s
Jul 11, 20263.1 s
Jul 18, 20263.1 s
Jul 25, 20263.2 s
Aug 1, 20263.4 s
Aug 8, 20263.2 s
Aug 15, 20263.2 s
Aug 22, 20263.0 s
Aug 29, 20262.9 s
Sep 5, 20262.8 s
Sep 12, 20262.6 s
Sep 19, 20262.6 s
Sep 26, 20262.2 s
Oct 3, 20262.3 s
Oct 10, 20262.2 s
Oct 17, 20262.2 s
Oct 24, 20262.3 s
Real-visitor tap response (INP)75th percentile, phones
121 ms82 msMay 9Oct 24102 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 202686 ms
May 16, 202686 ms
May 23, 202692 ms
May 30, 2026102 ms
Jun 6, 2026105 ms
Jun 13, 2026113 ms
Jun 20, 2026113 ms
Jun 27, 2026106 ms
Jul 4, 202698 ms
Jul 11, 202696 ms
Jul 18, 2026104 ms
Jul 25, 2026109 ms
Aug 1, 2026116 ms
Aug 8, 2026113 ms
Aug 15, 2026112 ms
Aug 22, 2026115 ms
Aug 29, 2026114 ms
Sep 5, 2026114 ms
Sep 12, 2026110 ms
Sep 19, 2026101 ms
Sep 26, 202687 ms
Oct 3, 202687 ms
Oct 10, 202688 ms
Oct 17, 2026101 ms
Oct 24, 2026102 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 amikids.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. amikids.org at 0.9 s0.9 s
  2. amikids.org at 1.9 s1.9 s
  3. amikids.org at 2.8 s2.8 s
  4. amikids.org at 3.7 s3.7 s
  5. amikids.org at 4.6 s4.6 s
  6. amikids.org at 5.6 s5.6 s
  7. amikids.org at 6.5 s6.5 s
  8. amikids.org at 7.4 s7.4 s

Speed

12 to fix41
  • Reduce unused JavaScript

    5.8 s · 1.7 MB

    About 1.7 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 5.8 s faster on a phone.

  • Improve image delivery

    3.4 s · 731 KiB

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

  • Use efficient cache lifetimes

    3.2 s · 641 KiB

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

  • Render-blocking requests

    3.8 s

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

  • classy.org adds 1.1 s

    1.1 s

    classy.org costs a phone 1.1 s of main-thread work and 1.1 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.

  • Mobile performance score: 41

    41/100

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

  • Main-thread work: 4.8 s

    A phone's processor spends 4.8 s on main-thread work while loading, 2.9 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 (classy.org, Google CDN and Google Tag Manager and others), adding 3.3 MB and 2.0 s of main-thread time.

  • Reduce unused CSS

    530 ms · 142 KiB

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

  • Google CDN adds 309 ms

    309 ms

    Google CDN costs a phone 309 ms of main-thread work and 858 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.

  • 14 long tasks on the main thread

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

  • Other Google APIs/SDKs adds 41 ms

    41 ms

    Other Google APIs/SDKs costs a phone 41 ms of main-thread work and 465 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 JavaScript

    150 ms · 6 KiB

    6 KiB could be saved by minifying JavaScript.

  • Minify CSS

    80 ms · 12 KiB

    12 KiB could be saved by minifying CSS.

  • Font display

    50 ms

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

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

    11 ms

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

Core Web Vitals

10 to fix50
  • 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: 10.6 s

    10.6 s

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

  • Largest Contentful Paint: 25.3 s

    25.3 s

    Your largest element takes 25.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

  • Time to Interactive: 39.1 s

    39.1 s

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

  • Speed Index: 14.5 s

    14.5 s

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

  • Real-user LCP: 2.7 s

    2.7 s

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

  • Real-user FCP: 2.3 s

    2.3 s

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

  • Real-user TTFB: 1.3 s

    1.3 s

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

  • Total Blocking Time: 555 ms

    555 ms

    Scripts block taps and scrolling for 555 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) got 18% slower for real visitors

    +18%

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

  • Largest content (LCP) held steady for real visitors

    +6%

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

2 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • Cumulative Layout Shift: 0.015

    0.015

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

Images and page weight

3 to fix53
  • Page weight: 12.2 MB in 213 requests

    12.2 MB

    Your homepage downloads 12.2 MB in 213 requests on a phone: images 6.7 MB (38), scripts 4.1 MB (87) and other files 857 KiB (59). Under 2 MB keeps phones on slow connections fast.

  • 2 images far larger than shown

    296 KiB

    2 images are downloaded at several times the size a phone draws them, for example Stock-Kid-cut-out-2.png.webp at 2,560 px wide, shown at 351 px. Resized copies would save about 296 KiB.

  • 2 images below the first screen load straight away

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

  • 2 images in older formats

    2 images (460 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 3.4 g of CO₂ per visit

    3.45 g

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

Accessibility

7 to fixGoogle 8489
  • 44 text elements with low contrast

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

  • ARIA input fields must have an accessible name (2 elements)

    ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

  • Interactive controls must not be nested (1 element)

    Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

  • 5 images without alt text

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

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

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

  • 20 links without text

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

  • No page language

    The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.

  • Headings skip levels

    Headings skip levels (h2 → h5), 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 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 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

2 to fixGoogle 8593
  • 3 H1 headlines

    There are 3 <h1> headlines (“This is where success happens”, “EMPOWERING YOUNG PEOPLE TO BELIEVE I CAN” and “What sets us apart? Experiential education.”). One clear main headline is easier for people and search engines.

  • 5 links crawlers can't follow

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

  • 76 internal links, 8 external

    The homepage links to 76 pages on amikids.org and 8 external pages.

7 checks passed
  • Meta description: 135 characters

    Your meta description is 135 characters: “AMIkids is a non-profit organization dedicated to empowering young people to discover their true potential. It’s where …”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “AMIkids Non-Profit Organization: Empowering Youth Since 1969”.

  • Canonical URL set

    The canonical URL is https://amikids.org/.

  • 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://amikids.org/sitemap_index.xml.

AI search readiness

100
  • No llms.txt

    There is no https://amikids.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.

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

Other pages

2 to fix93
  • 2 pages share a meta description

    https://amikids.org/about-amikids/national-spokesperson and https://amikids.org/about-amikids/experiential-education use the same meta description. A description written for each page earns more clicks.

  • 2 pages without an H1

    https://amikids.org/success-stories and https://amikids.org/our-press 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 29 found) and read each the way a search engine does.

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

  • 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

3 to fixGoogle 6985
  • 8 small tap targets

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

  • 2 third-party cookies

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

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “SiteSearch360 15.1.208 FAILED to initialize to #searchBox,.ss360-searchbox There is no input element for the searchBox.…”.

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

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

  • Thin social proof

    Social proof on the homepage: 14 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 900 words of visible text.

4 checks passed
  • 2 calls to action

    The homepage has 2 calls to action, for example “Learn more about Our Impact” and “Join our team”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 1 phone link 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 to fix
  • 4 trackers load before any consent

    4

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

  • 12 cookies set on arrival

    12

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

  • 33 other companies contacted

    Loading the homepage contacts 33 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 amikids.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
WordPress
Framework
jQuery
Analytics
Google Analytics | Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on amikids.org, including 22 speed issues, 2 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