Website review, no card needed
elephantrobotics.com website review
Visit site (opens in a new tab)Reviewed 5 November 202623 issues · 70 checks
This review found 23 issues worth fixing on elephantrobotics.com, 12 of them high impact, across 70 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 6.2 s |
| May 23, 2026 | 6.3 s |
| May 30, 2026 | 6.4 s |
| Jun 6, 2026 | 6.4 s |
| Jun 13, 2026 | 6.1 s |
| Jun 20, 2026 | 6.2 s |
| Jun 27, 2026 | 6.1 s |
| Jul 4, 2026 | 6.0 s |
| Jul 11, 2026 | 6.3 s |
| Jul 18, 2026 | 6.5 s |
| Jul 25, 2026 | 6.5 s |
| Aug 1, 2026 | 6.6 s |
| Aug 8, 2026 | 6.4 s |
| Aug 15, 2026 | 6.2 s |
| Aug 22, 2026 | 6.0 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 5.8 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 6.2 s |
| Sep 26, 2026 | 6.2 s |
| Oct 3, 2026 | 6.7 s |
| Oct 10, 2026 | 6.4 s |
| Oct 17, 2026 | 5.9 s |
| Oct 24, 2026 | 5.9 s |
| Oct 31, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 163 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 165 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 169 ms |
| Jun 27, 2026 | 153 ms |
| Jul 4, 2026 | 147 ms |
| Jul 11, 2026 | 147 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 164 ms |
| Aug 1, 2026 | 178 ms |
| Aug 8, 2026 | 187 ms |
| Aug 15, 2026 | 186 ms |
| Aug 22, 2026 | 185 ms |
| Aug 29, 2026 | 186 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 173 ms |
| Sep 19, 2026 | 167 ms |
| Sep 26, 2026 | 158 ms |
| Oct 3, 2026 | 164 ms |
| Oct 10, 2026 | 145 ms |
| Oct 17, 2026 | 170 ms |
| Oct 24, 2026 | 146 ms |
| Oct 31, 2026 | 150 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.8 s
1.6 s
2.3 s
3.1 s
3.9 s
4.7 s
5.4 s
6.2 s
Speed
Render-blocking requests
2.3 s32 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 86
86/100Your mobile performance score is 86. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
600 ms · 131 KiBAbout 131 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.
1,751 HTML elements
The page has 1,751 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
200 ms · 23 KiB34 files are served with short cache lifetimes, so returning visitors download them again (23 KiB).
Improve image delivery
20 KiB1 image could be 20 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
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 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 1 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 37 ms of it running JavaScript. That is comfortably low.
Server response: 292 ms
292 msYour server sent the HTML in 292 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.8 s
5.8 sReal visitors wait 5.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 5.0 s
5.0 sReal visitors see the first content after 5.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 8.8 s
8.8 sVisually, the page fills in at 8.8 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-7%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 163 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 6.2 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 163 ms
163 msReal visitors wait 163 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 2.4 s
2.4 sYour largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the image “600”.
Time to Interactive: 2.4 s
2.4 sThe page is fully interactive after 2.4 s.
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
About 0.1 g of CO₂ per visit
0.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.12 g of CO₂e: 14.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 427 KiB in 41 requests
427 KiBYour homepage downloads 427 KiB in 41 requests on a phone: stylesheets 201 KiB (32), images 181 KiB (7) and HTML 41 KiB (1). That is a lean page.
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
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
54 images without alt text
54 images have no alt text, which hurts accessibility and image search.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
42 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: 42 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (26 characters)
Your title is only 26 characters: “大象机器人官网|全球领先的轻量级机械臂与机器人开发商”. Between 30 and 65 characters leaves room to say what you do and for whom.
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.
179 internal links, 32 external
The homepage links to 179 pages on elephantrobotics.com and 32 external pages.
6 checks passed
One H1 headline
Your main headline reads: “订阅我们”.
Canonical URL set
The canonical URL is https://www.elephantrobotics.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.elephantrobotics.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.elephantrobotics.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.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and description; sameAs (social profiles) and contact details would complete it.
Other pages
2 pages slow to respond
https://www.elephantrobotics.com/mycobot-280-m5-2023-cn and https://www.elephantrobotics.com/mycobot-280jetsonnano-2023-cn took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 77 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
3 small tap targets
3 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css' from origin 'https://www.elephantrobotics.com' has been …”.
1 checks passed
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.
Only about 42 words
The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.
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 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics, Meta Pixel and Matomo.
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.
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 elephantrobotics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Alibaba Cloud
Company
- Headquarters
- Shenzhen
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on elephantrobotics.com, including 10 speed issues, 2 SEO issues and 5 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.