Website review, no card needed

newagetraining.com logo

newagetraining.com website review

Visit site (opens in a new tab)Reviewed 23 October 202633 issues · 85 checks

This review found 33 issues worth fixing on newagetraining.com, 10 of them high impact, across 85 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
5.2 s4.8 sMay 2Oct 175.0 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20264.9 s
May 9, 20265.0 s
May 16, 20264.9 s
May 23, 20264.9 s
May 30, 20264.8 s
Jun 6, 20264.8 s
Jun 13, 20264.8 s
Jun 20, 20265.0 s
Jun 27, 20265.0 s
Jul 4, 20265.0 s
Jul 11, 20265.1 s
Jul 18, 20265.0 s
Jul 25, 20265.1 s
Aug 1, 20265.1 s
Aug 8, 20265.0 s
Aug 15, 20264.9 s
Aug 22, 20264.8 s
Aug 29, 20264.8 s
Sep 5, 20264.9 s
Sep 12, 20265.0 s
Sep 19, 20265.0 s
Sep 26, 20265.1 s
Oct 3, 20265.0 s
Oct 10, 20265.0 s
Oct 17, 20265.0 s
Real-visitor tap response (INP)75th percentile, phones
139 ms100 msMay 2Oct 17134 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026106 ms
May 9, 2026108 ms
May 16, 2026104 ms
May 23, 2026109 ms
May 30, 2026117 ms
Jun 6, 2026120 ms
Jun 13, 2026117 ms
Jun 20, 2026121 ms
Jun 27, 2026124 ms
Jul 4, 2026115 ms
Jul 11, 2026119 ms
Jul 18, 2026117 ms
Jul 25, 2026114 ms
Aug 1, 2026119 ms
Aug 8, 2026116 ms
Aug 15, 2026112 ms
Aug 22, 2026115 ms
Aug 29, 2026116 ms
Sep 5, 2026119 ms
Sep 12, 2026124 ms
Sep 19, 2026120 ms
Sep 26, 2026121 ms
Oct 3, 2026121 ms
Oct 10, 2026126 ms
Oct 17, 2026134 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 newagetraining.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. newagetraining.com at 1.2 s1.2 s
  2. newagetraining.com at 2.3 s2.3 s
  3. newagetraining.com at 3.5 s3.5 s
  4. newagetraining.com at 4.6 s4.6 s
  5. newagetraining.com at 5.8 s5.8 s
  6. newagetraining.com at 7.0 s7.0 s
  7. newagetraining.com at 8.1 s8.1 s
  8. newagetraining.com at 9.3 s9.3 s

Speed

13 to fix54
  • Render-blocking requests

    4.5 s

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

  • Reduce unused JavaScript

    1.7 s · 762 KiB

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

  • Mobile performance score: 54

    54/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Google Maps and Google CDN and others), adding 2.0 MB and 629 ms of main-thread time.

  • Font display

    700 ms

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

  • Improve image delivery

    250 ms · 368 KiB

    10 images could be 368 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.

  • Reduce unused CSS

    450 ms · 81 KiB

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

  • Google Tag Manager adds 291 ms

    291 ms

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

  • Use efficient cache lifetimes

    280 KiB

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

  • Google Maps adds 220 ms

    220 ms

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

  • Main-thread work: 2.1 s

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

  • Google CDN adds 76 ms

    76 ms

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

  • Other Google APIs/SDKs adds 3 ms

    3 ms

    Other Google APIs/SDKs costs a phone 3 ms of main-thread work and 443 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.

  • 5 long tasks on the main thread

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

  • Minify JavaScript

    13 KiB

    13 KiB could be saved by minifying JavaScript.

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

  • Minify CSS

    3 KiB

    3 KiB could be saved by minifying CSS.

1 checks passed
  • Server response: 3 ms

    3 ms

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

Core Web Vitals

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

  • Real-user LCP: 5.8 s

    5.8 s

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

  • Real-user FCP: 5.0 s

    5.0 s

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

  • Largest Contentful Paint: 13.5 s

    13.5 s

    Your largest element takes 13.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Welcome To New Age Training Superior Instruction For Superi…”. Most of its time is resource load delay (6.4 s).

  • Speed Index: 16.1 s

    16.1 s

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

  • Time to Interactive: 14.5 s

    14.5 s

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

  • First Contentful Paint: 4.2 s

    4.2 s

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

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

    +21%

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

  • Largest content (LCP) held steady for real visitors

    +1%

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

4 checks passed
  • Real-user INP: 102 ms

    102 ms

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

    0.097

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

  • Total Blocking Time: 91 ms

    91 ms

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

Images and page weight

1 to fix85
  • Page weight: 3.2 MB in 183 requests

    3.2 MB

    Your homepage downloads 3.2 MB in 183 requests on a phone: scripts 1.7 MB (67), images 888 KiB (18) and fonts 383 KiB (8). Under 2 MB keeps phones on slow connections fast.

  • 2 images in older formats

    2 images (69 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.

  • 2 images below the first screen load straight away

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

  • About 0.9 g of CO₂ per visit

    0.90 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.3 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

4 to fixGoogle 9295
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

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

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

  • The skip-link target should exist and be focusable (1 element)

    The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

  • 1 form field without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 11 images in the HTML carry an alt attribute.

  • 42 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: 42 passed and 4 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 9290
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “New Age Training | Medical Assistant Training School New York, NYC”.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 80 internal links, 5 external

    The homepage links to 80 pages on newagetraining.com and 5 external pages.

7 checks passed
  • Meta description: 140 characters

    Your meta description is 140 characters: “New Age Training is Licensed and Accredited medical school in the heart of NYC for Medical Assistant, CNA, PCT and othe…”.

  • One H1 headline

    Your main headline reads: “Welcome To New Age Training”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList, 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://newagetraining.com/sitemap.xml.

AI search readiness

100
  • No llms.txt

    There is no https://newagetraining.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 (477 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix85
  • 4 pages without a meta description

    https://newagetraining.com/admissions, https://newagetraining.com/shop, https://newagetraining.com/privacy-policy and https://newagetraining.com/courses/medical-assistant 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://newagetraining.com/admissions, whose canonical is https://newagetraining.com/career/admissions-officer. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 9 pages without an H1

    https://newagetraining.com/admissions, https://newagetraining.com/student-services, https://newagetraining.com/testimonials, https://newagetraining.com/certifications-licenses, https://newagetraining.com/about-new-age-training and https://newagetraining.com/faq and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 pages slow to respond

    https://newagetraining.com/admissions, https://newagetraining.com/accredited-healthcare-training-nyc, https://newagetraining.com/student-services, https://newagetraining.com/testimonials, https://newagetraining.com/certifications-licenses and https://newagetraining.com/about-new-age-training and 8 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 26 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

Google 96100
  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix94
  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

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

    The homepage carries about 463 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Learn More!” and “Register Today!”.

  • 12 calls to action

    The homepage has 12 calls to action, for example “Shop”, “Orientation Schedule” and “Program/Class Schedule”.

  • 1 short form

    A short form (1 field at most) is right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 18 testimonial or review blocks and 1 trust badge.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 2 phone links and 2 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
  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

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

  • 10 other companies contacted

    Loading the homepage contacts 10 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 newagetraining.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
E-commerce
WooCommerce
Analytics
Google Analytics

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on newagetraining.com, including 21 speed issues, 2 SEO issues and 1 conversion gap. 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