Website review, no card needed
amiplastics.com website review
Visit site (opens in a new tab)Reviewed 30 October 202628 issues · 99 checks
This review found 28 issues worth fixing on amiplastics.com, 9 of them high impact, across 99 checks. The most urgent: reduce unused JavaScript. 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
80BClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.8 s |
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 4.1 s |
| May 30, 2026 | 4.1 s |
| Jun 6, 2026 | 4.3 s |
| Jun 13, 2026 | 4.4 s |
| Jun 20, 2026 | 5.4 s |
| Jun 27, 2026 | 4.0 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.1 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 4.0 s |
| Aug 8, 2026 | 4.4 s |
| Sep 5, 2026 | 3.9 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 3.8 s |
| Sep 26, 2026 | 3.8 s |
| Oct 3, 2026 | 3.1 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 169 ms |
| May 16, 2026 | 123 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 133 ms |
| Jun 13, 2026 | 155 ms |
| Sep 5, 2026 | 135 ms |
| Sep 12, 2026 | 120 ms |
| Sep 19, 2026 | 121 ms |
| Sep 26, 2026 | 134 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
amiplastics.com does not allow embedding, so this is Google's rendering of the page.
Speed
Reduce unused JavaScript
4.2 s · 580 KiBAbout 580 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.2 s faster on a phone.
Render-blocking requests
1.2 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.
Mobile performance score: 62
62/100Your mobile performance score is 62. 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 CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.2 MB and 681 ms of main-thread time.
Google CDN adds 405 ms
405 msGoogle CDN costs a phone 405 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.
Google Tag Manager adds 192 ms
192 msGoogle Tag Manager costs a phone 192 ms of main-thread work and 295 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.
Improve image delivery
200 ms · 33 KiB3 images could be 33 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Reduce unused CSS
130 ms · 33 KiBAbout 33 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 131 ms. During a long task the page ignores taps.
Legacy JavaScript
50 ms · 11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 50 ms faster on a phone.
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.
2 checks passed
Main-thread work: 1.8 s
A phone's processor spends 1.8 s on main-thread work while loading, 1.1 s of it running JavaScript. That is comfortably low.
Server response: 28 ms
28 msYour server sent the HTML in 28 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.
Largest Contentful Paint: 8.9 s
8.9 sYour largest element takes 8.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 13.4 s
13.4 sThe page becomes fully interactive after 13.4 s. Good is under 3.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
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.
Total Blocking Time: 305 ms
305 msScripts block taps and scrolling for 305 ms in total while the page loads. Good is under 200 ms.
5 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 169 ms to 134 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 26% faster for real visitors
-26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.2 s
1.2 sThe first text or image appears after 1.2 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 71 requests
2.2 MBYour homepage downloads 2.2 MB in 71 requests on a phone: scripts 1.3 MB (20), other files 410 KiB (21) and images 287 KiB (10). Under 2 MB keeps phones on slow connections fast.
About 0.6 g of CO₂ per visit
0.62 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.62 g of CO₂e: 74.4 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
<svg> elements with an img or image role must have alternative text (4 elements)
<svg> elements with an img or image role must have alternative text: 4 elements on the page fail this check, rated serious by axe-core.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 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 should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (6 elements).
2 checks passed
Every image has alt text
All 15 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 47 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
18 H1 headlines
There are 18 <h1> headlines (“Connecting the global plastics industry”, “Empowering industry leaders to thrive and innovate” and “Discover AMI”). One clear main headline is easier for people and search engines.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
65 internal links, 9 external
The homepage links to 65 pages on amiplastics.com and 9 external pages.
7 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “AMI is a leading information provider in the global plastics industry; providing expert knowledge, in-depth research, a…”.
Title: 56 characters
Your title is a healthy 56 characters: “AMI | Plastics Market Intelligence, Consultancy & Events”.
Canonical URL set
The canonical URL is https://www.amiplastics.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 and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.amiplastics.com/sitemap.xml.
AI search readiness
No llms.txt
There is no /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: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (875 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/terms-and-conditions-event-attendees and /terms-and-conditions-EU-exhibition-visitors all use the title “Terms and conditions - event attendees”. Search engines can't tell which page to show for a search, so each competes with the others.
3 pages share a meta description
/terms-and-conditions-event-attendees, /terms-and-conditions-EU-exhibition-visitors and /terms-and-conditions-USA-exhibition-visitors use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 29 found) and read each the way a search engine does.
6 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.
Every page has a meta description
All 15 pages that loaded have a meta description.
Every page has an H1
Each page we checked has a main headline.
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 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Minified React error #418; visit https://react.dev/errors/418?args[]=HTML&args[]= for the full message or use the non-m…”.
2 checks passed
Tap targets are thumb-sized
8 of 9 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Security and trust
9 checks passed
Served over HTTPS
The homepage is served over HTTPS (amiplastics.com).
Valid certificate (51 days left)
The certificate from DigiCert Inc · GeoTrust TLS RSA CA G1 verifies for amiplastics.com and is valid for another 51 days.
Protected from clickjacking
X-Frame-Options or a frame-ancestors policy stops other sites framing yours.
Content-Security-Policy set
A Content-Security-Policy is set, the main browser-side defence against injected scripts.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://amiplastics.com redirects to the secure version.
HTTP/2
The server speaks HTTP/2, so browsers load many files over one connection.
All 39 links work
All 39 links checked from your homepage (30 internal, 9 external) answered without errors.
security.txt published
A security.txt file tells researchers how to report a problem with your site.
Domain and trust
No CAA record
amiplastics.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.
DNSSEC is off
amiplastics.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.
2 checks passed
Domain is 28 years old
28 yearsamiplastics.com was registered in Sep 1998 through GoDaddy.com, LLC. An established domain carries more trust with email providers and search engines.
Registered until Sep 2027
amiplastics.com is registered until Sep 2027.
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.
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: 5 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 517 words of copy
The homepage carries about 517 words of visible text.
5 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
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.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication, and sends you reports.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:dc-34c065e1ae._spfm.amiplastics.com ~all”.
DKIM signing found
A DKIM key is published (selector “selector2”), so receivers can verify mail really came from you.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- Framework
- Next.js
- Analytics
- Google Tag Manager
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 28 issues on amiplastics.com, including 14 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.