26.5 sec in total
382 ms
25.7 sec
483 ms
Visit lele186.com now to see the best up-to-date Lele 186 content for China and also check out these interesting facts you probably never knew about lele186.com
Find cheapest for Refurbished Smartphones & Cellphones & smartphones & Pre-owned phones & Cell Phones accessories & Cell phones parts, pls email: Sales@lele186.com; Alice@lele186.com; Angel@lele186.co...
Visit lele186.comWe analyzed Lele186.com page load time and found that the first response time was 382 ms and then it took 26.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 12 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
lele186.com performance score
name
value
score
weighting
Value3.9 s
25/100
10%
Value7.9 s
3/100
25%
Value22.3 s
0/100
10%
Value4,980 ms
0/100
30%
Value0.388
26/100
15%
Value12.7 s
13/100
10%
382 ms
349 ms
18 ms
44 ms
56 ms
Our browser made a total of 92 requests to load all elements on the main page. We found that 93% of them (86 requests) were addressed to the original Lele186.com, 4% (4 requests) were made to Static.addtoany.com and 1% (1 request) were made to Wpa.qq.com. The less responsive or slowest element that took the longest time to load (20.3 sec) belongs to the original domain Lele186.com.
Page size can be reduced by 84.4 kB (14%)
600.3 kB
515.9 kB
In fact, the total size of Lele186.com main page is 600.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Images take 451.7 kB which makes up the majority of the site volume.
Potential reduce by 55.3 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.3 kB or 81% of the original size.
Potential reduce by 14.6 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. Lele 186 images are well optimized though.
Potential reduce by 11.6 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 11.6 kB or 18% of the original size.
Potential reduce by 2.9 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. Lele186.com needs all CSS files to be minified and compressed as it can save up to 2.9 kB or 18% of the original size.
Number of requests can be reduced by 15 (20%)
75
60
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lele 186. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
lele186.com
382 ms
www.lele186.com
349 ms
bootstrap.css
18 ms
bxslider.css
44 ms
style.css
56 ms
jquery.min.js
108 ms
bxslider.min.js
102 ms
common.js
100 ms
bootstrap.js
177 ms
font-awesome.min.css
209 ms
ionicons.min.css
233 ms
style.css
231 ms
jquery.smoove.min.js
229 ms
lang.js
232 ms
eonline.css
229 ms
online.js
239 ms
page.js
189 ms
pa
789 ms
facebook.png
139 ms
twitter.png
142 ms
linkedin.png
150 ms
google.png
146 ms
instagram.png
162 ms
youtube.png
167 ms
5bc6a3b9cca1e1574.png
173 ms
62e25382ba9a56874.jpg
6238 ms
62a83667bd4c72041.jpg
6449 ms
6184ef14853f85023.jpg
5001 ms
6215b55b728123223.jpg
7895 ms
62e358fcd731d1302.jpg
17278 ms
6188a2ac784345392.jpg
1377 ms
61889bba08fa44082.jpg
2498 ms
6188967ed917f6401.jpg
5860 ms
5d7202ae2a27d418.jpg
14367 ms
5d71f9505cd341086.jpg
9857 ms
5c10d87e2ee6c9433.jpg
8316 ms
5bf23998e47003890.jpg
12237 ms
5c88806d06c1a110.jpg
14744 ms
5cda8b47c26dc725.jpg
9567 ms
5cda7043a50098658.jpg
10395 ms
5c88d590c81d32540.jpg
11838 ms
5c88ce88334a0172.jpg
17466 ms
5bc5b441c83842948.jpg
12871 ms
5bc5b0aac6e0d2031.jpg
15190 ms
5bc5a737626147074.jpg
14177 ms
5bc5a77286d9e5327.jpg
20314 ms
5c35966883d362425.jpg
20314 ms
5bc6aec6dcd068558.jpg
14963 ms
5bc6a844599578862.jpg
16428 ms
5bc6a0f58001e3972.jpg
17789 ms
5bc817a7d6a9f8252.jpg
20313 ms
15414295295bc696a5d566d4997.jpg
19202 ms
5bc8226a201547079.jpg
18319 ms
5bc960867fd791164.jpg
20193 ms
5caeb21a229ca685.jpg
20189 ms
5c3c51197caba7877.jpg
20184 ms
5bc6cfb010a9a4008.jpg
20180 ms
5bc6b7eec43da4680.jpg
20168 ms
5bc18c222df8c8732.png
20163 ms
5bc18c77b3f3e6773.png
20156 ms
glyphicons-halflings-regular.woff
20155 ms
eso.e18d3993.js
28 ms
icons.30.svg.js
34 ms
sm.23.html
49 ms
fontawesome-webfont.woff
19941 ms
5bc18ca33e3601732.png
18041 ms
button_121.gif
883 ms
5bc18cca5c1e96378.png
15553 ms
5ce21d394d6177026.jpg
17990 ms
596c638d501bd.jpg
17187 ms
ico_deutsch1.gif
13903 ms
ico_espanol.gif
12457 ms
ico_francies.gif
12036 ms
ico_italino.gif
10788 ms
ico_portgues.gif
10502 ms
ico_japan.jpg
13218 ms
ico_korea.jpg
9771 ms
ico_arabia.jpg
11629 ms
ico_russia.jpg
8450 ms
skype.gif
7147 ms
5bc6dae12b108710.jpg
8001 ms
bx_loader.gif
7096 ms
line.gif
6890 ms
5bc18dae5e6335355.jpg
7101 ms
controls.png
5864 ms
panel-bg.png
5237 ms
top.png
5116 ms
middle.png
4749 ms
bottom.png
4240 ms
cmsfloatqrcodepanel-hd-bg.gif
3374 ms
glyphicons-halflings-regular.ttf
3139 ms
fontawesome-webfont.ttf
3219 ms
lele186.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-hidden="true"] elements contain focusable descendents
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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
lele186.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
lele186.com 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lele186.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lele186.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.
lele186.com
Open Graph description is not detected on the main page of Lele 186. 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: