8.1 sec in total
385 ms
7.2 sec
514 ms
Welcome to lensgo.net homepage info - get ready to check LENSGO best content right away, or after learning these important things about lensgo.net
Lensgo was established in 2011 and is pursuing to be a audio wireless microphone manufacturer. Through the efforts of the team, it has become a fashionable and creative high-quality manufacturer of 3C...
Visit lensgo.netWe analyzed Lensgo.net page load time and found that the first response time was 385 ms and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lensgo.net performance score
name
value
score
weighting
Value3.4 s
39/100
10%
Value7.9 s
3/100
25%
Value14.2 s
1/100
10%
Value2,150 ms
6/100
30%
Value0
100/100
15%
Value38.7 s
0/100
10%
385 ms
89 ms
68 ms
242 ms
1187 ms
Our browser made a total of 134 requests to load all elements on the main page. We found that 63% of them (84 requests) were addressed to the original Lensgo.net, 9% (12 requests) were made to Rode.com and 8% (11 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (4.5 sec) belongs to the original domain Lensgo.net.
Page size can be reduced by 2.2 MB (16%)
14.0 MB
11.9 MB
In fact, the total size of Lensgo.net main page is 14.0 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 13.7 MB which makes up the majority of the site volume.
Potential reduce by 47.5 kB
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 10.2 kB, which is 17% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.5 kB or 80% of the original size.
Potential reduce by 2.1 MB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, LENSGO needs image optimization as it can save up to 2.1 MB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 31.7 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 31.7 kB or 15% of the original size.
Potential reduce by 11.1 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Lensgo.net has all CSS files already compressed.
Number of requests can be reduced by 54 (47%)
114
60
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LENSGO. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
lensgo.net
385 ms
js
89 ms
js
68 ms
rBQBG116ASmEA7CjAAAAAM7mhg04870.js
242 ms
69.js
1187 ms
css-OpenSans400italic400700.css
62 ms
myrodereel_font_load.css
118 ms
jquery-ui.min.css
118 ms
style-1608614861.css
196 ms
font-awesome.min.css
118 ms
liyingjia.css
118 ms
main.css
118 ms
home_blog-20201222.css
168 ms
aboutus-20201222.css
168 ms
js
81 ms
homebanner.js
192 ms
jquery-1.7.2.min.js
192 ms
popwin.js
191 ms
jquery-1.11.1.min.js
228 ms
rodemic.js
217 ms
mobile-detect.js
220 ms
jquery.fancybox.css
226 ms
jquery.fancybox.js
228 ms
home-20201222.js
225 ms
js
57 ms
analytics.js
35 ms
56 ms
collect
33 ms
collect
36 ms
33 ms
ga-audiences
27 ms
ga.js
6 ms
__utm.gif
12 ms
collect
12 ms
ga-audiences
17 ms
69.js
890 ms
hm.js
1062 ms
css-PlayfairDisplay400400i700_la.css
59 ms
css-FiraSans400500700.css
57 ms
css-Roboto400700.css
56 ms
lensgo.png
85 ms
1638954866885285.png
87 ms
burger.png
85 ms
drawer_close.png
87 ms
language.png
86 ms
1697163255374523.jpg
1138 ms
1697165403900981.jpg
571 ms
1697165435508685.jpg
824 ms
1688174097405589.jpg
980 ms
1688174221687976.jpg
1036 ms
1679885094357899.jpg
578 ms
1679722636812295.jpg
1085 ms
1679722556380509.jpg
1401 ms
1679722591325989.jpg
1701 ms
1679722524564694.jpg
2576 ms
1679885065106225.jpg
2114 ms
1679885078796031.jpg
1499 ms
nexImg.png
1190 ms
preImg.png
1243 ms
1697165057266657.jpg
1811 ms
1697160204318046.png
2070 ms
1697160110997792.png
2171 ms
1646472546904361.jpg
1804 ms
1646472378498372.jpg
1906 ms
1646471851924869.jpg
1965 ms
1646470569505306.jpg
2061 ms
1646381118626610.jpg
2173 ms
1646380534356754.jpg
2218 ms
1646378565295396.jpg
2174 ms
1646277214745884.jpg
2215 ms
1618625920220926.png
2582 ms
1618626327687007.png
4470 ms
1618811956917575.png
2586 ms
1618833314252752.png
2812 ms
1620091859172424.png
3010 ms
66 ms
pages_56.html
2704 ms
1619256656206314.png
3152 ms
1620351079967176.png
3366 ms
social_facebook.png
2677 ms
social_twitter.png
2728 ms
avenir-book-webfont.woff
2917 ms
avenir-book-webfont.svg
145 ms
36 ms
avenir-black-webfont.svg
125 ms
avenir-book-webfont.svg
260 ms
avenir-black-webfont.svg
246 ms
avenir-book-webfont.svg
945 ms
avenir-black-webfont.svg
936 ms
fontawesome-webfont-4.3.0.woff
2443 ms
glyphicons-halflings-regular.woff
2439 ms
social_instagram.png
2191 ms
hm.gif
295 ms
social_lingying.png
2037 ms
social_whatsapp.png
2091 ms
youtube1.png
2041 ms
1638954770872129.png
2049 ms
1679724576349061.jpg
2080 ms
1679724304672990.jpg
1946 ms
1679724765976212.jpg
2098 ms
avenir-black-webfont.woff
1738 ms
1627958467859602.jpg
1647 ms
3f_play_left.png
1479 ms
3f_play_right.png
1485 ms
s2.png
1480 ms
t2.png
1382 ms
s3.png
1338 ms
s8.png
1331 ms
s7.png
1377 ms
mo7h.png
1281 ms
motop.png
1280 ms
232 ms
228 ms
__utm.gif
210 ms
avenir-book-webfont.svg
216 ms
avenir-black-webfont.svg
216 ms
116 ms
collect
65 ms
110 ms
95 ms
90 ms
hm.gif
298 ms
__utm.gif
38 ms
collect
38 ms
hm.gif
566 ms
avenir-book-webfont.svg
66 ms
avenir-black-webfont.svg
63 ms
15 ms
17 ms
avenir-black-webfont.svg
1273 ms
avenir-book-webfont.svg
827 ms
__utm.gif
4 ms
__utm.gif
24 ms
__utm.gif
8 ms
lensgo.net accessibility score
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.
Impact
Issue
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a valid value for its [lang] attribute.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
lensgo.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lensgo.net SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
EN
CN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lensgo.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Lensgo.net main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
lensgo.net
Open Graph description is not detected on the main page of LENSGO. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: