Website review, no card needed

astm.org logo

astm.org website review

Visit site (opens in a new tab)Reviewed 17 November 202639 issues · 83 checks

This review found 39 issues worth fixing on astm.org, 15 of them high impact, across 83 checks. The most urgent: page weight: 25.8 MB in 100 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
6.7 s3.9 sMay 30Nov 144.2 s
Show as table
DateReal-visitor load time (LCP)
May 30, 20266.3 s
Jun 6, 20266.2 s
Jun 13, 20266.1 s
Jun 20, 20266.2 s
Jun 27, 20266.3 s
Jul 4, 20266.3 s
Jul 11, 20266.4 s
Jul 18, 20266.2 s
Jul 25, 20266.1 s
Aug 1, 20266.2 s
Aug 8, 20266.2 s
Aug 15, 20266.3 s
Aug 22, 20266.2 s
Aug 29, 20266.0 s
Sep 5, 20265.8 s
Sep 12, 20265.6 s
Sep 19, 20265.7 s
Sep 26, 20265.8 s
Oct 3, 20265.9 s
Oct 10, 20265.8 s
Oct 17, 20265.6 s
Oct 24, 20265.3 s
Oct 31, 20264.9 s
Nov 7, 20264.4 s
Nov 14, 20264.2 s
Real-visitor tap response (INP)75th percentile, phones
238 ms132 msMay 30Nov 14144 ms
Show as table
DateReal-visitor tap response (INP)
May 30, 2026223 ms
Jun 6, 2026224 ms
Jun 13, 2026226 ms
Jun 20, 2026225 ms
Jun 27, 2026225 ms
Jul 4, 2026225 ms
Jul 11, 2026224 ms
Jul 18, 2026219 ms
Jul 25, 2026220 ms
Aug 1, 2026221 ms
Aug 8, 2026219 ms
Aug 15, 2026221 ms
Aug 22, 2026217 ms
Aug 29, 2026213 ms
Sep 5, 2026206 ms
Sep 12, 2026206 ms
Sep 19, 2026209 ms
Sep 26, 2026210 ms
Oct 3, 2026215 ms
Oct 10, 2026218 ms
Oct 17, 2026209 ms
Oct 24, 2026195 ms
Oct 31, 2026179 ms
Nov 7, 2026149 ms
Nov 14, 2026144 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 astm.org (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

8 to fix34
  • Reduce unused JavaScript

    1.2 s · 598 KiB

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

  • Render-blocking requests

    1.5 s

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

  • Mobile performance score: 34

    34/100

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

  • Improve image delivery

    150 ms · 862 KiB

    7 images could be 862 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.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Optanon and Hotjar and others), adding 1.0 MB and 621 ms of main-thread time.

  • Google Tag Manager adds 463 ms

    463 ms

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

  • Reduce unused CSS

    300 ms · 78 KiB

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

  • Font display

    350 ms

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

  • 7 long tasks on the main thread

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

  • Use efficient cache lifetimes

    67 KiB

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

  • Legacy JavaScript

    20 KiB

    Polyfills for old browsers add 20 KiB JavaScript that modern phones do not need.

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

    2 KiB

    2 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.9 s

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

  • Server response: 65 ms

    65 ms

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

Core Web Vitals

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

    4.9 s

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

  • Real-user FCP: 4.0 s

    4.0 s

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

  • Real-user TTFB: 2.4 s

    2.4 s

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

  • Largest Contentful Paint: 8.7 s

    8.7 s

    Your largest element takes 8.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Compass_BSI”.

  • Time to Interactive: 16.9 s

    16.9 s

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

  • Cumulative Layout Shift: 0.692

    0.692

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

  • Real-user CLS: 0.21

    0.21

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

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Total Blocking Time: 412 ms

    412 ms

    Scripts block taps and scrolling for 412 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.

3 checks passed
  • Real-user INP: 156 ms

    156 ms

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

  • Tap response (INP) got 34% faster for real visitors

    -34%

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

  • Largest content (LCP) got 31% faster for real visitors

    -31%

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

Images and page weight

2 to fix64
  • Page weight: 25.8 MB in 100 requests

    25.8 MB

    Your homepage downloads 25.8 MB in 100 requests on a phone: media 22.7 MB (1), scripts 1.4 MB (34) and images 1,010 KiB (12). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    Compass_BSI.png 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).

  • 4 images in older formats

    4 images (315 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 7.3 g of CO₂ per visit

    7.32 g

    By the Sustainable Web Design model, a visit to your homepage emits about 7.32 g of CO₂e: 878.8 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 8993
  • 2 buttons without a name

    2 buttons have no accessible name, so screen readers announce just “button”.

  • 6 text elements with low contrast

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

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

  • Headings skip levels

    Headings skip levels (h4 → h6, h4 → h6 and h4 → h6), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 19 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 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 39 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 9272
  • No H1 headline

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

  • Title is short (25 characters)

    Your title is only 25 characters: “ASTM International | ASTM”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • No structured data

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

  • Meta description is long (231 characters)

    Your meta description is 231 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 10 links with vague text

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

  • 64 internal links, 16 external

    The homepage links to 64 pages on astm.org and 16 external pages.

4 checks passed
  • Canonical URL set

    The canonical URL is https://www.astm.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.

  • XML sitemap found

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

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

Other pages

2 to fix90
  • 13 pages without a meta description

    https://www.astm.org/about, https://www.astm.org/about/global-cooperation, https://www.astm.org/about/corporate-citizenship, https://www.astm.org/about/history, https://www.astm.org/about/diversity-inclusion and https://www.astm.org/about/careers and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.astm.org/about, https://www.astm.org/about/governance, https://www.astm.org/about/global-cooperation, https://www.astm.org/about/corporate-citizenship, https://www.astm.org/about/history and https://www.astm.org/about/locations/regional-offices-and-support and 9 others 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 45 found) and read each the way a search engine does.

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

  • 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 9693
  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix69
  • 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.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • No direct contact details

    No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

  • No opening hours

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

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

    The homepage carries about 881 words of visible text.

4 checks passed
  • 15 calls to action

    The homepage has 15 calls to action, for example “Contact ASTM”, “Contact Us” and “Learn more”.

  • 2 short forms

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

  • Social proof on the page

    Social proof on the homepage: 1 trust badge and “more than 35,000 members”.

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and LinkedIn Insight (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.

  • 15 cookies set on arrival

    15

    Opening the homepage sets 15 cookies, 2 of them by other companies (measured from a US location before any click).

  • 15 other companies contacted

    Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) loads with the page.

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 astm.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
Next.js
Analytics
Google Tag Manager
Hosting
CloudFront

Company

Employees
311
Founded
1898
Headquarters
West Conshohocken

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 astm.org, including 20 speed issues, 5 SEO issues and 4 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