Website review, no card needed
actnano.com website review
Visit site (opens in a new tab)Reviewed 20 October 202633 issues · 77 checks
This review found 33 issues worth fixing on actnano.com, 13 of them high impact, across 77 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 5.4 s |
| May 9, 2026 | 5.3 s |
| May 16, 2026 | 5.2 s |
| May 23, 2026 | 5.1 s |
| May 30, 2026 | 5.0 s |
| Jun 6, 2026 | 5.0 s |
| Jun 13, 2026 | 5.0 s |
| Jun 20, 2026 | 5.0 s |
| Jun 27, 2026 | 5.1 s |
| Jul 4, 2026 | 5.2 s |
| Jul 11, 2026 | 5.3 s |
| Jul 18, 2026 | 5.3 s |
| Jul 25, 2026 | 5.4 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.3 s |
| Aug 15, 2026 | 5.3 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 4.7 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 2.7 s |
| Sep 19, 2026 | 2.7 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 199 ms |
| May 9, 2026 | 194 ms |
| May 16, 2026 | 189 ms |
| May 23, 2026 | 183 ms |
| May 30, 2026 | 185 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 191 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 192 ms |
| Jul 4, 2026 | 204 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 216 ms |
| Jul 25, 2026 | 205 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 192 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 198 ms |
| Aug 29, 2026 | 188 ms |
| Sep 5, 2026 | 177 ms |
| Sep 12, 2026 | 114 ms |
| Sep 19, 2026 | 116 ms |
| Sep 26, 2026 | 87 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 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
Speed
Improve image delivery
1.6 s · 4.4 MB11 images could be 4.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.6 s faster on a phone.
Reduce unused JavaScript
3.9 s · 747 KiBAbout 747 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.9 s faster on a phone.
Render-blocking requests
3.6 s30 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.6 s.
Mobile performance score: 44
44/100Your mobile performance score is 44 (desktop: 41). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
7 third-party services on the page
7 third-party services load with your homepage (YouTube, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.3 MB and 814 ms of main-thread time.
Reduce unused CSS
600 ms · 192 KiBAbout 192 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
YouTube adds 520 ms
520 msYouTube costs a phone 520 ms of main-thread work and 967 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
400 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 400 ms).
Main-thread work: 3.8 s
A phone's processor spends 3.8 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 281 ms
281 msGoogle Tag Manager costs a phone 281 ms of main-thread work and 311 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.
9 long tasks on the main thread
9 long tasks block the main thread while loading, the longest for 233 ms. During a long task the page ignores taps.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Use efficient cache lifetimes
1 KiB3 files are served with short cache lifetimes, so returning visitors download them again (1 KiB).
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 10.1 s
10.1 sThe first text or image appears after 10.1 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 20.0 s
20.0 sYour largest element takes 20.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies and similar technologies to operate the webs…”.
Time to Interactive: 20.1 s
20.1 sThe page becomes fully interactive after 20.1 s. Good is under 3.8 s.
Speed Index: 11.1 s
11.1 sVisually, the page fills in at 11.1 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 456 ms
456 msScripts block taps and scrolling for 456 ms in total while the page loads. Good is under 200 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
3 checks passed
Tap response (INP) got 51% faster for real visitors
-51%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 199 ms to 96 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 54% faster for real visitors
-54%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 5.4 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 8.3 MB in 112 requests
8.3 MBYour homepage downloads 8.3 MB in 112 requests on a phone: images 6.1 MB (22), scripts 1.5 MB (35) and fonts 422 KiB (7). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
658 KiB3 images are downloaded at several times the size a phone draws them, for example actnano-difference-scaled.jpg at 2,560 px wide, shown at 390 px. Resized copies would save about 658 KiB.
4 images in older formats
4 images (1.2 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.
2 images below the first screen load straight away
2 images further down the page (358 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.4 g of CO₂ per visit
2.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.36 g of CO₂e: 282.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 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
29 links with vague text
29 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
60 internal links, 14 external
The homepage links to 60 pages on actnano.com and 14 external pages.
8 checks passed
Meta description: 111 characters
Your meta description is 111 characters: “PFAS-Free PCBA coating alternative for traditional conformal coatings, offering IPx8 protection for electronics”.
One H1 headline
Your main headline reads: “actnano Home Page”.
Title: 39 characters
Your title is a healthy 39 characters: “PFAS-Free Conformal Coating Alternative”.
Canonical URL set
The canonical URL is https://actnano.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, 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.
XML sitemap found
Your XML sitemap is reachable at https://actnano.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://actnano.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,151 words), so crawlers that don't run JavaScript still read it.
Other pages
2 pages share a title
/ and https://actnano.com/pfas-free all use the title “PFAS-free Conformal Coating Alternative”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://actnano.com/ai-data-infrastructure has no meta description, so Google writes the search snippet from whatever text it finds.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://actnano.com/consumer-electronics, whose canonical is https://actnano.com/consumer-electronics-coatings. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 19 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.
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
5 third-party cookies
5 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 “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
7 of 8 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 467 words of copy
The homepage carries about 467 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Get Started”.
15 calls to action
The homepage has 15 calls to action, for example “Contact Us”, “Get Started” and “Learn More”.
1 short form
A short form (5 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (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.
3 cookies set on arrival
3Opening the homepage sets 3 cookies, 1 of them by other companies (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.
13 other companies contacted
Loading the homepage contacts 13 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 actnano.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2023.
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on actnano.com, including 16 speed issues, 1 SEO issue and 2 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.