26.2 sec in total
2.1 sec
23.5 sec
601 ms
Visit 86yr.com now to see the best up-to-date 86 Yr content for United States and also check out these interesting facts you probably never knew about 86yr.com
Shenzhen Yaorong Technology Co., Ltd. is a powerful manufacturer integrating independent research and development, production and sales of LED lamps
Visit 86yr.comWe analyzed 86yr.com page load time and found that the first response time was 2.1 sec and then it took 24.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
86yr.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value17.3 s
0/100
25%
Value9.2 s
13/100
10%
Value850 ms
34/100
30%
Value0.288
42/100
15%
Value15.9 s
6/100
10%
2078 ms
857 ms
1296 ms
2185 ms
875 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 99% of them (68 requests) were addressed to the original 86yr.com, 1% (1 request) were made to Download.skype.com. The less responsive or slowest element that took the longest time to load (19.7 sec) belongs to the original domain 86yr.com.
Page size can be reduced by 757.4 kB (34%)
2.2 MB
1.5 MB
In fact, the total size of 86yr.com main page is 2.2 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. 25% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.
Potential reduce by 44.8 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 11.8 kB, which is 23% 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 44.8 kB or 88% of the original size.
Potential reduce by 556.2 kB
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, 86 Yr needs image optimization as it can save up to 556.2 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 127.9 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 127.9 kB or 71% of the original size.
Potential reduce by 28.5 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. 86yr.com needs all CSS files to be minified and compressed as it can save up to 28.5 kB or 80% of the original size.
Number of requests can be reduced by 6 (9%)
68
62
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 86 Yr. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and as a result speed up the page load time.
86yr.com
2078 ms
comm.css
857 ms
index.css
1296 ms
jquery-1.8.0.min.js
2185 ms
comm.js
875 ms
index.js
876 ms
jq.marq.js
875 ms
common.css
1285 ms
kefu.js
1746 ms
skypeCheck.js
6 ms
slider.js
1331 ms
backup.jpg
435 ms
zg.jpg
444 ms
yw.jpg
490 ms
rb.jpg
446 ms
20150423113607_7969.jpg
1817 ms
20150415120736ico_6594.jpg
972 ms
20150427083846ico_4485.jpg
893 ms
20150427084000ico_5736.jpg
911 ms
20150425160011ico_3516.jpg
910 ms
20150425160327ico_9454.jpg
971 ms
20150425160524ico_6172.jpg
1330 ms
20150425162802ico_2427.jpg
1376 ms
20150425163242ico_1493.jpg
1347 ms
20150425163116ico_6181.jpg
1454 ms
20150424114500ico_9682.jpg
1455 ms
20150424114926ico_3918.jpg
1781 ms
20150424115803ico_1451.jpg
1783 ms
20150427113556ico_8893.jpg
1811 ms
20150427115829ico_2960.jpg
1906 ms
20150427115937ico_2335.jpg
1906 ms
20150427110346ico_0137.jpg
2232 ms
20150427110940ico_3107.jpg
2246 ms
20150427120515ico_4211.jpg
2262 ms
20150427121020ico_0619.jpg
2278 ms
20150427111440ico_6078.jpg
2370 ms
pic_user1.png
3619 ms
pic_user2.png
3165 ms
pic_user3.png
2807 ms
pic_user4.png
3430 ms
pic_user5.png
3491 ms
pic_user6.png
3552 ms
pic_user7.png
3784 ms
20150409113000_3457.jpg
19654 ms
20150409112401_0644.jpg
7215 ms
20150409113523_3300.jpg
6593 ms
20141028111807_1497.jpg
4826 ms
pic_fyk.png
4485 ms
about_more.jpg
4008 ms
20141029160209_0008.jpg
6844 ms
20141029160128_9383.jpg
6315 ms
20141029160037_7352.jpg
7051 ms
20141029155952_0008.jpg
7861 ms
20141029155744_0949.jpg
7938 ms
20141029155659_2824.jpg
8437 ms
20141029155546_9699.jpg
8547 ms
20141029155501_5480.jpg
8642 ms
20141029155411_6888.jpg
9091 ms
bg_nav1.png
8720 ms
icoa.png
8952 ms
nav_bg.png
8952 ms
20150326164736_0158.jpg
11621 ms
20150326164801_5626.jpg
13382 ms
20150326164844_3595.jpg
12432 ms
imga.png
9529 ms
p1.jpg
9468 ms
foot_tel.jpg
10200 ms
dot.png
9889 ms
ad_ctr.png
10624 ms
86yr.com 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
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
Heading elements are not in a sequentially-descending order
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.
86yr.com 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
86yr.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 86yr.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that 86yr.com 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.
86yr.com
Open Graph description is not detected on the main page of 86 Yr. 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: