Website review, no card needed
aoyiladder.com website review
Visit site (opens in a new tab)Reviewed 10 November 202624 issues · 70 checks
This review found 24 issues worth fixing on aoyiladder.com, 6 of them high impact, across 70 checks. The most urgent: 6 pages point its canonical at the homepage. 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
78CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Mobile performance score: 81
81/100Your mobile performance score is 81. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
800 ms13 files block the first paint until they finish downloading. Deferring or inlining them could save about 800 ms.
Use efficient cache lifetimes
400 ms · 238 KiB34 files are served with short cache lifetimes, so returning visitors download them again (238 KiB).
Improve image delivery
218 KiB4 images could be 218 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
150 ms · 51 KiBAbout 51 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
2 third-party services on the page
2 third-party services load with your homepage (Cloudflare and Google Fonts), adding 94 KiB and 11 ms of main-thread time.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
2 checks passed
Main-thread work: 1.0 s
A phone's processor spends 1.0 s on main-thread work while loading, 117 ms of it running JavaScript. That is comfortably low.
Server response: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 4.2 s
4.2 sYour largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is element render delay (2.0 s).
Speed Index: 4.8 s
4.8 sVisually, the page fills in at 4.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 4.2 s
4.2 sThe page becomes fully interactive after 4.2 s. Good is under 3.8 s.
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.
2 checks passed
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
4 images far larger than shown
342 KiB4 images are downloaded at several times the size a phone draws them, for example 4_1_5a7381.jpg at 685 px wide, shown at 30 px. Resized copies would save about 342 KiB.
5 images in older formats
5 images (384 KiB) 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 0.2 g of CO₂ per visit
0.23 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.23 g of CO₂e: 28.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 845 KiB in 41 requests
845 KiBYour homepage downloads 845 KiB in 41 requests on a phone: images 458 KiB (8), fonts 155 KiB (4) and scripts 135 KiB (16). That is a lean page.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
All page content should be contained by landmarks (60 elements)
All page content should be contained by landmarks: 60 elements on the page fail this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
19 links without text
19 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 22 images in the HTML carry an alt attribute.
46 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
93 internal links, 0 external
The homepage links to 93 pages on aoyiladder.com and 0 external pages.
5 checks passed
Meta description: 148 characters
Your meta description is 148 characters: “Leading manufacturer of aluminum ladders, telescopic ladders, step ladders & scaffolding platforms. Quality constructio…”.
Title: 57 characters
Your title is a healthy 57 characters: “Premium Aluminum Ladders & Work Platforms - Aoyi Industry”.
Canonical URL set
The canonical URL is https://aoyiladder.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at http://aoyiladder.com/sitemap_index.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://aoyiladder.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
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,337 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages point its canonical at the homepage
https://aoyiladder.com/%22https://www.websiteclosers.com/sell-your-business-by-industry/sell-saas-business/%22, https://aoyiladder.com/%22https://www.websiteclosers.com//%22, https://aoyiladder.com/%22https://www.websiteclosers.com/franchise/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-business-brokers/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-city-business-brokers/%22 and https://aoyiladder.com/%22https://www.websiteclosers.com/locations/buffalo-business-broker/%22 declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.
7 pages share a title
/, https://aoyiladder.com/%22https://www.websiteclosers.com/sell-your-business-by-industry/sell-saas-business/%22, https://aoyiladder.com/%22https://www.websiteclosers.com//%22, https://aoyiladder.com/%22https://www.websiteclosers.com/franchise/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-business-brokers/%22 and https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-city-business-brokers/%22 and 1 other all use the title “Premium Aluminum Ladders & Work Platforms - Aoyi Industry”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://aoyiladder.com/articles, https://aoyiladder.com/about-us, https://aoyiladder.com/our-contacts and https://aoyiladder.com/category/main have no meta description, so Google writes the search snippet from whatever text it finds.
6 pages share a meta description
https://aoyiladder.com/%22https://www.websiteclosers.com/sell-your-business-by-industry/sell-saas-business/%22, https://aoyiladder.com/%22https://www.websiteclosers.com//%22, https://aoyiladder.com/%22https://www.websiteclosers.com/franchise/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-business-brokers/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-city-business-brokers/%22 and https://aoyiladder.com/%22https://www.websiteclosers.com/locations/buffalo-business-broker/%22 use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://aoyiladder.com/%22https://www.websiteclosers.com/sell-your-business-by-industry/sell-saas-business/%22, https://aoyiladder.com/%22https://www.websiteclosers.com//%22, https://aoyiladder.com/%22https://www.websiteclosers.com/franchise/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-business-brokers/%22, https://aoyiladder.com/%22https://www.websiteclosers.com/locations/new-york-city-business-brokers/%22 and https://aoyiladder.com/%22https://www.websiteclosers.com/locations/buffalo-business-broker/%22 have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://aoyiladder.com/about-us and https://aoyiladder.com/our-contacts 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.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
80 of 83 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
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 1,492 words of copy
The homepage carries about 1,492 words of visible text.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
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.
3 other companies contacted
Loading the homepage contacts 3 hosts 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 aoyiladder.com, 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
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 24 issues on aoyiladder.com, including 7 speed issues, 3 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.