Bothsh.com Site Title

Freeze Dryer, Wiped Film, Short Path - BOTH

Bothsh.com Meta Description

BOTH Instrument & Industrial Equipment (Shanghai) Co., Ltd. is a technical innovation enterprise integrating research & development, design, and

Bothsh.com Test Results

Bothsh.com Mobile Performance: 35/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,540 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn how to minimize third-party impact.
Reduce JavaScript execution time
2.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Defer offscreen images
Potential savings of 65 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Minimize main-thread work
2.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Eliminate render-blocking resources
Potential savings of 1,020 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Largest Contentful Paint element
12,990 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 165 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid large layout shifts
15 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Reduce unused CSS
Potential savings of 37 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Properly size images
Potential savings of 468 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Serve static assets with an efficient cache policy
71 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid an excessive DOM size
1,530 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Avoid enormous network payloads
Total size was 2,677 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
Max Potential First Input Delay
1,180 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Time to Interactive
13.2 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.

Bothsh.com Mobile SEO: 77/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
7 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Bothsh.com Mobile Best Practices: 52/100
Quick overview:
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
Browser errors were logged to the console
Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
Bothsh.com Mobile Accessibility: 80/100
Quick overview:
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.
Similar tests
www.bothsh.com
www.bothsh.net
www.bothsh.org
www.bothsh.info
www.bothsh.biz
www.bothsh.us
www.bothsh.mobi
www.othsh.com
www.bothsh.com
www.vothsh.com
www.bvothsh.com
www.vbothsh.com
www.gothsh.com
www.bgothsh.com
www.gbothsh.com
www.hothsh.com
www.bhothsh.com
www.hbothsh.com
www.nothsh.com
www.bnothsh.com
www.nbothsh.com
www.bthsh.com
www.bithsh.com
www.boithsh.com
www.biothsh.com
www.bkthsh.com
www.bokthsh.com
www.bkothsh.com
www.blthsh.com
www.bolthsh.com
www.blothsh.com
www.bpthsh.com
www.bopthsh.com
www.bpothsh.com
www.bohsh.com
www.borhsh.com
www.botrhsh.com
www.borthsh.com
www.bofhsh.com
www.botfhsh.com
www.bofthsh.com
www.boghsh.com
www.botghsh.com
www.bogthsh.com
www.boyhsh.com
www.botyhsh.com
www.boythsh.com
www.botsh.com
www.botbsh.com
www.bothbsh.com
www.botbhsh.com
www.botgsh.com
www.bothgsh.com
www.botysh.com
www.bothysh.com
www.botush.com
www.bothush.com
www.botuhsh.com
www.botjsh.com
www.bothjsh.com
www.botjhsh.com
www.botnsh.com
www.bothnsh.com
www.botnhsh.com
www.bothh.com
www.bothwh.com
www.bothswh.com
www.bothwsh.com
www.botheh.com
www.bothseh.com
www.bothesh.com
www.bothdh.com
www.bothsdh.com
www.bothdsh.com
www.bothzh.com
www.bothszh.com
www.bothzsh.com
www.bothxh.com
www.bothsxh.com
www.bothxsh.com
www.bothah.com
www.bothsah.com
www.bothash.com
www.boths.com
www.bothsb.com
www.bothshb.com
www.bothsbh.com
www.bothsg.com
www.bothshg.com
www.bothsgh.com
www.bothsy.com
www.bothshy.com
www.bothsyh.com
www.bothsu.com
www.bothshu.com
www.bothsuh.com
www.bothsj.com
www.bothshj.com
www.bothsjh.com
www.bothsn.com
www.bothshn.com
www.bothsnh.com
www.bothsh.con
Last Tested: