Website review, no card needed
aisin.com website review
Visit site (opens in a new tab)Reviewed 29 October 202646 issues · 87 checks
This review found 46 issues worth fixing on aisin.com, 20 of them high impact, across 87 checks. The most urgent: use efficient cache lifetimes. 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
62DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.4 s |
| May 16, 2026 | 5.3 s |
| May 23, 2026 | 5.5 s |
| May 30, 2026 | 5.4 s |
| Jun 6, 2026 | 5.6 s |
| Jun 13, 2026 | 5.9 s |
| Jun 20, 2026 | 5.5 s |
| Jun 27, 2026 | 5.4 s |
| Jul 4, 2026 | 5.4 s |
| Jul 11, 2026 | 5.2 s |
| Jul 18, 2026 | 5.0 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 5.0 s |
| Aug 8, 2026 | 4.9 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 5.7 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 6.1 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 6.5 s |
| Sep 26, 2026 | 6.1 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.4 s |
| Oct 17, 2026 | 5.3 s |
| Oct 24, 2026 | 5.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 168 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 173 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 178 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 168 ms |
| Jul 4, 2026 | 165 ms |
| Jul 11, 2026 | 160 ms |
| Jul 18, 2026 | 135 ms |
| Jul 25, 2026 | 124 ms |
| Aug 8, 2026 | 113 ms |
| Aug 15, 2026 | 149 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 162 ms |
| Sep 5, 2026 | 162 ms |
| Sep 12, 2026 | 184 ms |
| Sep 26, 2026 | 206 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 202 ms |
| Oct 17, 2026 | 207 ms |
| Oct 24, 2026 | 209 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
Use efficient cache lifetimes
1.9 s · 17.7 MB17 files are served with short cache lifetimes, so returning visitors download them again (17.7 MB).
Improve image delivery
10.5 s · 9.2 MB20 images could be 9.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 10.5 s faster on a phone.
Reduce unused JavaScript
3.5 s · 635 KiBAbout 635 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.5 s faster on a phone.
Render-blocking requests
2.3 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
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.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and datasign.co and others), adding 1.7 MB and 1.1 s of main-thread time.
Google Tag Manager adds 713 ms
713 msGoogle Tag Manager costs a phone 713 ms of main-thread work and 982 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.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 1.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
datasign.co adds 104 ms
104 msdatasign.co costs a phone 104 ms of main-thread work and 322 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
160 ms · 14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.
Minify JavaScript
160 ms · 9 KiB9 KiB could be saved by minifying JavaScript.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 154 ms. During a long task the page ignores taps.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
1 checks passed
Server response: 2 ms
2 msYour server sent the HTML in 2 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 LCP: 5.5 s
5.5 sReal visitors wait 5.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.8 s
1.8 sReal visitors wait 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 44.0 s
44.0 sYour largest element takes 44.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We may use unique personal identifiers (such as cookies) in…”.
Time to Interactive: 45.6 s
45.6 sThe page becomes fully interactive after 45.6 s. Good is under 3.8 s.
Speed Index: 11.7 s
11.7 sVisually, the page fills in at 11.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user INP: 208 ms
208 msReal visitors wait 208 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 26% slower for real visitors
+26%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 168 ms to 209 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 416 ms
416 msScripts block taps and scrolling for 416 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.4 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
Images and page weight
Page weight: 29.0 MB in 126 requests
29.0 MBYour homepage downloads 29.0 MB in 126 requests on a phone: media 17.4 MB (4), images 9.7 MB (52) and scripts 1.7 MB (29). Under 2 MB keeps phones on slow connections fast.
3 images over 500 KB
3 images weigh 6.7 MB together. On a phone connection a single image that size takes seconds.
5 images far larger than shown
6.6 MB5 images are downloaded at several times the size a phone draws them, for example d4d81696fff24e56f6ea171816673cae-thumb-6000x3000-12032.jpg at 6,000 px wide, shown at 332 px. Resized copies would save about 6.6 MB.
7 images in older formats
7 images (7.4 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 8.2 g of CO₂ per visit
8.22 gBy the Sustainable Web Design model, a visit to your homepage emits about 8.22 g of CO₂e: 986.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
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 37 images in the HTML carry an alt attribute.
40 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: 40 passed and 4 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (217 characters)
Your meta description is 217 characters; Google truncates after about 160, so the end of your pitch is cut.
No XML sitemap
No XML sitemap at https://aisin.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at aisin.com/robots.txt, the first file search crawlers ask for.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
One H1 headline
Your <h1> is empty.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
133 internal links, 7 external
The homepage links to 133 pages on aisin.com and 7 external pages.
2 checks passed
Title: 32 characters
Your title is a healthy 32 characters: “AISIN CORPORATION Global Website”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
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://aisin.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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (561 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages share a meta description
https://aisin.com/en/news, https://aisin.com/en/product, https://aisin.com/en/product/mobility, https://aisin.com/en/product/energy, https://aisin.com/en/product/mobility/new-other and https://aisin.com/en/technology and 6 others 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 73 found) and read each the way a search engine does.
7 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.
Titles are unique
Every page we checked has its own title.
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 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to manifest at 'https://www.aisin.com/en/manifest.json' from origin 'https://aisin.com' has been blocked by CORS…”.
2 distorted images
2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
56 of 64 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.
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 471 words of copy
The homepage carries about 471 words of visible text.
3 checks passed
6 calls to action
The homepage has 6 calls to action, for example “Sustainability Data Book”, “Sustainability Data Book 2026” and “FAQ/Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity 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.
29 cookies set on arrival
29Opening the homepage sets 29 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.
29 other companies contacted
Loading the homepage contacts 29 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 aisin.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Imperva
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on aisin.com, including 21 speed issues, 7 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.