Website review, no card needed
bo-re-tech.com website review
Visit site (opens in a new tab)Reviewed 3 November 202641 issues · 80 checks
This review found 41 issues worth fixing on bo-re-tech.com, 20 of them high impact, across 80 checks. The most urgent: font display. 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.9 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.0 s |
| Jun 6, 2026 | 4.0 s |
| Jun 13, 2026 | 3.8 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.7 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.5 s |
| Aug 8, 2026 | 3.5 s |
| Aug 15, 2026 | 3.5 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.7 s |
| Sep 19, 2026 | 3.9 s |
| Sep 26, 2026 | 4.3 s |
| Oct 3, 2026 | 4.8 s |
| Oct 10, 2026 | 4.7 s |
| Oct 17, 2026 | 4.9 s |
| Oct 24, 2026 | 4.6 s |
| Oct 31, 2026 | 4.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 101 ms |
| May 23, 2026 | 96 ms |
| May 30, 2026 | 96 ms |
| Jun 6, 2026 | 99 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 99 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 105 ms |
| Jul 18, 2026 | 113 ms |
| Jul 25, 2026 | 112 ms |
| Aug 1, 2026 | 108 ms |
| Aug 8, 2026 | 105 ms |
| Aug 15, 2026 | 101 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 102 ms |
| Sep 5, 2026 | 98 ms |
| Sep 12, 2026 | 101 ms |
| Sep 19, 2026 | 99 ms |
| Sep 26, 2026 | 101 ms |
| Oct 3, 2026 | 115 ms |
| Oct 10, 2026 | 113 ms |
| Oct 17, 2026 | 115 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 127 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
1.6 s
3.1 s
4.7 s
6.2 s
7.8 s
9.3 s
10.9 s
12.4 s
Speed
Font display
3.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 3.0 s).
Reduce unused JavaScript
1.5 s · 207 KiBAbout 207 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
300 ms · 5.3 MB12 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Render-blocking requests
850 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 850 ms.
Use efficient cache lifetimes
50 ms · 664 KiB45 files are served with short cache lifetimes, so returning visitors download them again (664 KiB).
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Clarity and pola-cloud.com.tw and others), adding 613 KiB and 516 ms of main-thread time.
Google Tag Manager adds 410 ms
410 msGoogle Tag Manager costs a phone 410 ms of main-thread work and 509 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.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 188 ms. During a long task the page ignores taps.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page.
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.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 562 ms of it running JavaScript. That is comfortably low.
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: 4.6 s
4.6 sReal visitors wait 4.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.10
1.10For real visitors the layout shifts by 1.10 (75th percentile). Good is under 0.1.
Real-user FCP: 3.4 s
3.4 sReal visitors see the first content after 3.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.9 s
1.9 sReal visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 1.726
1.726The layout shifts by 1.726 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest Contentful Paint: 18.2 s
18.2 sYour largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is resource load delay (8.8 s).
Speed Index: 13.8 s
13.8 sVisually, the page fills in at 13.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 19.0 s
19.0 sThe page becomes fully interactive after 19.0 s. Good is under 3.8 s.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 101 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
26 images without width and height
26 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.9 s to 4.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 127 ms
127 msReal visitors wait 127 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 181 ms
181 msScripts block the page for only 181 ms while loading. Good is under 200 ms.
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 6.6 MB in 71 requests
6.6 MBYour homepage downloads 6.6 MB in 71 requests on a phone: images 5.9 MB (28), scripts 679 KiB (20) and stylesheets 38 KiB (9). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.7 MB together. On a phone connection a single image that size takes seconds.
10 images far larger than shown
2.5 MB10 images are downloaded at several times the size a phone draws them, for example tray-20250626小_pic.png at 1,920 px wide, shown at 390 px. Resized copies would save about 2.5 MB.
11 images in older formats
11 images (5.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.
1 image below the first screen load straight away
1 image further down the page (849 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.9 g of CO₂ per visit
1.87 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.87 g of CO₂e: 224.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
8 buttons without a name
8 buttons have no accessible name, so screen readers announce just “button”.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 checks passed
Every image has alt text
All 26 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Structured data has 1 problem
Structured data found (Organization) but with 1 problem, for example “Organization: missing name”.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at bo-re-tech.com/robots.txt, the first file search crawlers ask for.
7 links crawlers can't follow
7 links have no real href, so search engines can't follow them.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
151 internal links, 16 external
The homepage links to 151 pages on bo-re-tech.com and 16 external pages.
5 checks passed
Meta description: 147 characters
Your meta description is 147 characters: “BoReTech is a world Leading PET bottle recycling washing plant Manufacturer with more 2 decades PET bottle recycling an…”.
One H1 headline
Your main headline reads: “PET BOTTLE RECYCLING SOLUTION”.
Title: 58 characters
Your title is a healthy 58 characters: “PET Bottle Recycling Washing Plant Manufacturer - Boretech”.
Canonical URL set
The canonical URL is https://www.bo-re-tech.com/en/index.html.
XML sitemap found
Your XML sitemap is reachable at https://www.bo-re-tech.com/sitemap.xml.
AI search readiness
Organization data is thin (2 of 6 facts)
Your Organization JSON-LD is missing name, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no https://www.bo-re-tech.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 (706 words), so crawlers that don't run JavaScript still read it.
Other pages
6 pages share a title
https://www.bo-re-tech.com/en/solution/PET-TRAY.html, https://www.bo-re-tech.com/en/solution/Efficient-and-Smart---PET-Bottle-Recycling-Solution.html, https://www.bo-re-tech.com/en/solution/Flexible-Plastic-Recycling-Solution.html, https://www.bo-re-tech.com/en/solution/Comprehensive-recycling-solution-for-PP-PE-caps-material.html, https://www.bo-re-tech.com/en/solution/PO-Rigid-Plastic-Recycling---Washing-Solution-for-Post-Consumer-Waste.html and https://www.bo-re-tech.com/en/solution/ECOSPIN.html all use the title “ZHEJIANG BORETECH ENVIRONMENTAL ENGINEERING CO., LTD.”. Search engines can't tell which page to show for a search, so each competes with the others.
7 pages without a meta description
https://www.bo-re-tech.com/en/solution/PET-TRAY.html, https://www.bo-re-tech.com/en/solution/Efficient-and-Smart---PET-Bottle-Recycling-Solution.html, https://www.bo-re-tech.com/en/solution/Flexible-Plastic-Recycling-Solution.html, https://www.bo-re-tech.com/en/solution/Comprehensive-recycling-solution-for-PP-PE-caps-material.html, https://www.bo-re-tech.com/en/solution/PO-Rigid-Plastic-Recycling---Washing-Solution-for-Post-Consumer-Waste.html and https://www.bo-re-tech.com/en/solution/POY-Plant-Filamant-Yarn-Producton-Line.html and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.
1 page slow to respond
https://www.bo-re-tech.com/en/solution/Efficient-and-Smart---PET-Bottle-Recycling-Solution.html took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 45 found) and read each the way a search engine does.
5 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 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
18 small tap targets
18 of 42 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://webdesign.pola-cloud.com.tw/js/fancybox/jquery.fancybox.min.css' from origin 'http…”.
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 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 220 words
The homepage has only about 220 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.
3 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Contact”, “Join US” and “Download Center”.
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 Tag Manager.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
2 other companies contacted
Loading the homepage contacts 2 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 bo-re-tech.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 © 2025.
Stack
- Framework
- jQuery
- Analytics
- Google Tag Manager
- Hosting
- Data Communication Business Group
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on bo-re-tech.com, including 19 speed issues, 5 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.