Website review, no card needed
ameristarperimeter.com website review
Visit site (opens in a new tab)Reviewed 19 November 202635 issues · 80 checks
This review found 35 issues worth fixing on ameristarperimeter.com, 10 of them high impact, across 80 checks. The most urgent: improve image delivery. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 2.3 s |
| Jun 6, 2026 | 2.4 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.6 s |
| Jun 27, 2026 | 2.4 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.8 s |
| Aug 15, 2026 | 1.8 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 2.0 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 2.1 s |
| Nov 7, 2026 | 2.1 s |
| Nov 14, 2026 | 2.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 175 ms |
| Jun 6, 2026 | 179 ms |
| Jun 13, 2026 | 179 ms |
| Jun 20, 2026 | 179 ms |
| Jun 27, 2026 | 179 ms |
| Jul 4, 2026 | 179 ms |
| Jul 11, 2026 | 179 ms |
| Jul 18, 2026 | 176 ms |
| Jul 25, 2026 | 175 ms |
| Aug 1, 2026 | 177 ms |
| Aug 8, 2026 | 174 ms |
| Aug 15, 2026 | 172 ms |
| Aug 22, 2026 | 172 ms |
| Aug 29, 2026 | 172 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 175 ms |
| Sep 19, 2026 | 178 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 181 ms |
| Oct 10, 2026 | 181 ms |
| Oct 17, 2026 | 180 ms |
| Oct 24, 2026 | 181 ms |
| Oct 31, 2026 | 179 ms |
| Nov 7, 2026 | 179 ms |
| Nov 14, 2026 | 186 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.7 s
1.4 s
2.1 s
2.9 s
3.6 s
4.3 s
5.0 s
5.7 s
Speed
Improve image delivery
3.0 s · 604 KiB2 images could be 604 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Use efficient cache lifetimes
2.3 s · 707 KiB41 files are served with short cache lifetimes, so returning visitors download them again (707 KiB).
Mobile performance score: 49
49/100Your mobile performance score is 49. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
3 third-party services on the page
3 third-party services load with your homepage (Optanon, Google Tag Manager and assaabloy.com), adding 1.3 MB and 716 ms of main-thread time.
Render-blocking requests
800 ms11 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Reduce unused JavaScript
769 KiBAbout 769 KiB of JavaScript is downloaded but never used on this page.
Optanon adds 325 ms
325 msOptanon costs a phone 325 ms of main-thread work and 162 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 331 ms. During a long task the page ignores taps.
Google Tag Manager adds 272 ms
272 msGoogle Tag Manager costs a phone 272 ms of main-thread work and 325 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.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
assaabloy.com adds 119 ms
119 msassaabloy.com costs a phone 119 ms of main-thread work and 876 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
14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
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: 3 ms
3 msYour server sent the HTML in 3 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.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Largest Contentful Paint: 6.2 s
6.2 sYour largest element takes 6.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 7.8 s
7.8 sVisually, the page fills in at 7.8 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 203 ms
203 msReal visitors wait 203 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.25
0.25For real visitors the layout shifts by 0.25 (75th percentile). Good is under 0.1.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.238
0.238The layout shifts by 0.238 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 372 ms
372 msScripts block taps and scrolling for 372 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) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 175 ms to 186 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 2.3 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 2.9 MB in 56 requests
2.9 MBYour homepage downloads 2.9 MB in 56 requests on a phone: scripts 1.8 MB (24), images 818 KiB (6) and fonts 193 KiB (4). Under 2 MB keeps phones on slow connections fast.
About 0.8 g of CO₂ per visit
0.83 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.83 g of CO₂e: 99.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
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
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 36 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 1 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (16 characters)
Your title is only 16 characters: “Home | Ameristar”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (232 characters)
Your meta description is 232 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (BreadcrumbList and VideoObject) but with 1 problem, for example “VideoObject: thumbnailUrl is not an absolute URL ("https://gw-assets.assaabloy.com/is/image/assaabl…”.
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.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
9 internal links, 0 external
The homepage links to 9 pages on ameristarperimeter.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “Ameristar Perimeter Security”.
Canonical URL set
The canonical URL is https://www.ameristarperimeter.com/us/en.
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.ameristarperimeter.com/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://www.ameristarperimeter.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.
1 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.
Other pages
1 page without an H1
https://www.ameristarperimeter.com/us/en/resources/news-updates/news/ameristar-perimeter-security-and-jerith-manufacturing-achieve-iso-14001-certification has no <h1> headline, so visitors and search engines get no clear main topic.
8 pages with very little text
https://www.ameristarperimeter.com/us/en/products, https://www.ameristarperimeter.com/us/en/resources/digital-catalog, https://www.ameristarperimeter.com/us/en/products/ornamental-fence-gates, https://www.ameristarperimeter.com/us/en/products/engineered-gates, https://www.ameristarperimeter.com/us/en/products/high-security-fence and https://www.ameristarperimeter.com/us/en/products/security-bollards and 2 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
9 internal pages checked
We fetched 9 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 9 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 9 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 9 pages that loaded have a <title>.
Best practices
Missing source maps
Large scripts ship without source maps.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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.
Only about 61 words
The homepage has only about 61 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
1 call to action
The homepage has 1 call to action, for example “Download Resources (all products)”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 other company contacted
Loading the homepage contacts 1 host run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 ameristarperimeter.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Analytics
- Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on ameristarperimeter.com, including 22 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.