Website review, no card needed
americanstaffing.net website review
Visit site (opens in a new tab)Reviewed 25 October 202650 issues · 99 checks
This review found 50 issues worth fixing on americanstaffing.net, 19 of them high impact, across 99 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.7 s |
| May 9, 2026 | 3.5 s |
| May 16, 2026 | 3.4 s |
| May 23, 2026 | 3.5 s |
| May 30, 2026 | 3.4 s |
| Jun 6, 2026 | 3.5 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.7 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 4.1 s |
| Jul 11, 2026 | 4.2 s |
| Jul 18, 2026 | 4.2 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.8 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.7 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.7 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.7 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.7 s |
| Oct 10, 2026 | 3.7 s |
| Oct 17, 2026 | 3.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 152 ms |
| May 9, 2026 | 146 ms |
| May 16, 2026 | 147 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 145 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 142 ms |
| Jul 4, 2026 | 134 ms |
| Jul 11, 2026 | 143 ms |
| Jul 18, 2026 | 144 ms |
| Jul 25, 2026 | 140 ms |
| Aug 1, 2026 | 137 ms |
| Aug 8, 2026 | 135 ms |
| Aug 15, 2026 | 134 ms |
| Aug 22, 2026 | 134 ms |
| Aug 29, 2026 | 129 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 131 ms |
| Sep 19, 2026 | 142 ms |
| Sep 26, 2026 | 142 ms |
| Oct 3, 2026 | 138 ms |
| Oct 10, 2026 | 144 ms |
| Oct 17, 2026 | 129 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
How it loaded on a phone
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Render-blocking requests
9.5 s44 files block the first paint until they finish downloading. Deferring or inlining them could save about 9.5 s.
Reduce unused JavaScript
1.9 s · 739 KiBAbout 739 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 55). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.7 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 (Google Tag Manager, FontAwesome CDN and cloudfront.net and others), adding 3.4 MB and 2.1 s of main-thread time.
Use efficient cache lifetimes
550 ms · 470 KiB26 files are served with short cache lifetimes, so returning visitors download them again (470 KiB).
Google Tag Manager adds 721 ms
721 msGoogle Tag Manager costs a phone 721 ms of main-thread work and 367 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
460 ms · 110 KiBAbout 110 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 460 ms faster on a phone.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 564 ms. During a long task the page ignores taps.
cloudfront.net adds 320 ms
320 mscloudfront.net costs a phone 320 ms of main-thread work and 2.0 MB 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.
FontAwesome CDN adds 406 ms
406 msFontAwesome CDN costs a phone 406 ms of main-thread work and 180 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.
2,511 HTML elements
The page has 2,511 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 139 ms
139 msGoogle CDN costs a phone 139 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.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Improve image delivery
194 KiB3 images could be 194 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
48 KiBPolyfills for old browsers add 48 KiB JavaScript that modern phones do not need.
Minify JavaScript
21 KiB21 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.
1 checks passed
Server response: 32 ms
32 msYour server sent the HTML in 32 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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 FCP: 3.6 s
3.6 sReal visitors see the first content after 3.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 11.4 s
11.4 sThe first text or image appears after 11.4 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 25.0 s
25.0 sYour largest element takes 25.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The expertise to grow. The network to succeed.”.
Time to Interactive: 32.1 s
32.1 sThe page becomes fully interactive after 32.1 s. Good is under 3.8 s.
Speed Index: 11.4 s
11.4 sVisually, the page fills in at 11.4 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 707 ms
707 msScripts block taps and scrolling for 707 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.8 s
3.8 sReal visitors wait 3.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 152 ms to 129 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-17, real Chrome visitors' largest content (lcp) went from 3.7 s to 3.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 120 ms
120 msReal visitors wait 120 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 6.0 MB in 253 requests
6.0 MBYour homepage downloads 6.0 MB in 253 requests on a phone: images 2.9 MB (56), scripts 1.8 MB (55) and fonts 1.1 MB (19). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
2026-Playbook-cover-3D-trimmed-transparent-744x1024.png weighs 766 KiB. On a phone connection a single image that size takes seconds.
20 images in older formats
20 images (2.3 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.
About 1.7 g of CO₂ per visit
1.71 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.71 g of CO₂e: 204.7 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
Certain ARIA roles must be contained by particular parents (8 elements)
Certain ARIA roles must be contained by particular parents: 8 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
18 text elements with low contrast
18 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
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 → h4 and h1 → h3), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (29 characters)
Your title is only 29 characters: “American Staffing Association”. Between 30 and 65 characters leaves room to say what you do and for whom.
8 links with vague text
8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
266 internal links, 28 external
The homepage links to 266 pages on americanstaffing.net and 28 external pages.
7 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “American Staffing Association is the voice of the U.S. staffing, recruiting, and workforce solutions industry.”.
One H1 headline
Your main headline reads: “The expertise to grow. The network to succeed.”.
Canonical URL set
The canonical URL is https://americanstaffing.net/visit-asa-store/.
Structured data in place
Structured data found: BreadcrumbList, 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://americanstaffing.net/sitemap.xml.
AI search readiness
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://americanstaffing.net/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,721 words), so crawlers that don't run JavaScript still read it.
Other pages
3 pages without a meta description
https://americanstaffing.net/legal-2/asa-joint-employment-tool-kit, https://americanstaffing.net/legal-2/asa-indemnity-tool-kit and https://americanstaffing.net/legal-2/marijuana-the-workplace have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://americanstaffing.net/legal-2/harassment-prevention-training-for-your-temporary-workers and https://americanstaffing.net/acakitresources use the same meta description. A description written for each page earns more clicks.
5 links to non-canonical URLs
Your homepage links to 5 pages by a URL that isn't their canonical one, for example https://americanstaffing.net/legal/asa-lawyers, whose canonical is https://americanstaffing.net/legal-2/asa-lawyers. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
1 page without an H1
https://americanstaffing.net/legal-2/harassment-prevention-training-for-your-temporary-workers has no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://americanstaffing.net/asa, https://americanstaffing.net/legal/asa-lawyers, https://americanstaffing.net/legal/advocacy-public-policy and https://americanstaffing.net/acakitresources took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 183 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
7 small tap targets
7 of 27 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 (Not Found)”.
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Mixed content”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 572 words of copy
The homepage carries about 572 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Join”.
20 calls to action
The homepage has 20 calls to action, for example “Join”, “Download ASA Member Logos” and “Call for Presenters”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 1 more (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
15Opening 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.
36 other companies contacted
Loading the homepage contacts 36 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 americanstaffing.net, 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 Tag Manager
Company
- Founded
- 1966
- Headquarters
- Alexandria
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 50 issues on americanstaffing.net, including 23 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.