Website review, no card needed

ascls.org logo

ascls.org website review

Visit site (opens in a new tab)Reviewed 5 November 202637 issues · 79 checks

This review found 37 issues worth fixing on ascls.org, 18 of them high impact, across 79 checks. The most urgent: use efficient cache lifetimes. 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
4.7 s3.5 sMay 16Oct 313.7 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20264.0 s
May 23, 20264.1 s
May 30, 20264.1 s
Jun 6, 20263.8 s
Jun 13, 20263.8 s
Jun 20, 20263.9 s
Jun 27, 20264.0 s
Jul 4, 20264.1 s
Jul 11, 20264.1 s
Jul 18, 20263.9 s
Jul 25, 20263.9 s
Aug 1, 20263.9 s
Aug 8, 20264.0 s
Aug 15, 20264.2 s
Aug 22, 20264.3 s
Aug 29, 20264.5 s
Sep 5, 20264.3 s
Sep 12, 20264.1 s
Sep 19, 20264.0 s
Sep 26, 20263.9 s
Oct 3, 20264.0 s
Oct 10, 20263.9 s
Oct 17, 20263.8 s
Oct 24, 20263.6 s
Oct 31, 20263.7 s
Real-visitor tap response (INP)75th percentile, phones
204 ms120 msMay 16Oct 31146 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026140 ms
May 23, 2026141 ms
May 30, 2026144 ms
Jun 6, 2026137 ms
Jun 13, 2026143 ms
Jun 20, 2026135 ms
Jun 27, 2026133 ms
Jul 4, 2026143 ms
Jul 11, 2026151 ms
Jul 18, 2026156 ms
Jul 25, 2026156 ms
Aug 1, 2026194 ms
Aug 8, 2026165 ms
Aug 15, 2026185 ms
Aug 22, 2026177 ms
Aug 29, 2026158 ms
Sep 5, 2026152 ms
Sep 12, 2026133 ms
Sep 19, 2026130 ms
Sep 26, 2026140 ms
Oct 3, 2026156 ms
Oct 10, 2026156 ms
Oct 17, 2026161 ms
Oct 24, 2026152 ms
Oct 31, 2026146 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 ascls.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ascls.org at 0.4 s0.4 s
  2. ascls.org at 0.8 s0.8 s
  3. ascls.org at 1.1 s1.1 s
  4. ascls.org at 1.5 s1.5 s
  5. ascls.org at 1.9 s1.9 s
  6. ascls.org at 2.3 s2.3 s
  7. ascls.org at 2.6 s2.6 s
  8. ascls.org at 3.0 s3.0 s

Speed

8 to fix31
  • Use efficient cache lifetimes

    17.5 s · 4.1 MB

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

  • Render-blocking requests

    9.5 s

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

  • Reduce unused JavaScript

    7.5 s · 1.6 MB

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

  • Reduce unused CSS

    6.2 s · 1.0 MB

    About 1.0 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 6.2 s faster on a phone.

  • Mobile performance score: 31

    31/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and informz.net and others), adding 1.3 MB and 574 ms of main-thread time.

  • Improve image delivery

    400 ms · 129 KiB

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

  • Google Tag Manager adds 327 ms

    327 ms

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

  • Legacy JavaScript

    200 ms · 67 KiB

    Polyfills for old browsers add 67 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.

  • 8 long tasks on the main thread

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

  • Document request latency

    123 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • Minify JavaScript

    72 KiB

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

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

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

  • Server response: 149 ms

    149 ms

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

Core Web Vitals

11 to fix0
  • 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: 4.2 s

    4.2 s

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

  • Real-user CLS: 0.48

    0.48

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

  • First Contentful Paint: 10.7 s

    10.7 s

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

  • Largest Contentful Paint: 24.0 s

    24.0 s

    Your largest element takes 24.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Emerging Laboratory Managers Collaborative Conference”.

  • Time to Interactive: 35.9 s

    35.9 s

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

  • Speed Index: 10.7 s

    10.7 s

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

  • Cumulative Layout Shift: 0.338

    0.338

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

  • Real-user FCP: 3.0 s

    3.0 s

    Real visitors see the first content after 3.0 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: 342 ms

    342 ms

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

  • Tap response (INP) held steady for real visitors

    +6%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

Images and page weight

1 to fix70
  • Page weight: 5.3 MB in 139 requests

    5.3 MB

    Your homepage downloads 5.3 MB in 139 requests on a phone: scripts 3.5 MB (61), stylesheets 1.1 MB (32) and HTML 190 KiB (5). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (164 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.5 g of CO₂ per visit

    1.51 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • 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 9193
  • Frames without titles

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

  • 5 form fields without a label

    5 form fields have no label, so screen readers announce an empty box and autofill guesses.

2 checks passed
  • Every image has alt text

    All 25 images in the HTML carry an alt attribute.

  • 38 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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

5 to fixGoogle 9273
  • No H1 headline

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

  • Title is short (12 characters)

    Your title is only 12 characters: “Home - ASCLS”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is short (9 characters)

    Your meta description is only 9 characters: “Read More”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

  • 172 internal links, 53 external

    The homepage links to 172 pages on ascls.org and 53 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

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

Other pages

100
  • 15 internal pages checked

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

1 checks passed
  • Linked pages load

    All 15 pages we checked loaded without an error.

Best practices

2 to fixGoogle 7391
  • 4 third-party cookies

    4 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 “vc_initVideoBackgrounds is not defined”.

  • Browser-reported issues

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

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix64
  • 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 opening hours

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

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

    The homepage carries about 437 words of visible text.

4 checks passed
  • 3 calls to action

    The homepage has 3 calls to action, for example “Join” and “Register”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage, asking for an email.

  • Analytics in place

    Analytics detected: Google Analytics and Meta Pixel.

  • Phone number on the homepage

    Your phone number is on the homepage.

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

  • 15 cookies set on arrival

    15

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

  • 17 other companies contacted

    Loading the homepage contacts 17 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 ascls.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
Hosting
InMotion Hosting, Inc.

Hiring

Hiring
2 open roles
Job board
careers page

Company

Founded
1933
Headquarters
McLean

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on ascls.org, including 19 speed issues, 5 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