17.6 sec in total
3.3 sec
13.9 sec
441 ms
Click here to check amazing Lenoxx content for Brazil. Otherwise, check out these important facts you probably never knew about lenoxx.com.br
Adicionar aqui uma boa descrição da sua loja virtual. Esta descrição será mostrada nos resultados de busca do Google.
Visit lenoxx.com.brWe analyzed Lenoxx.com.br page load time and found that the first response time was 3.3 sec and then it took 14.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lenoxx.com.br performance score
3278 ms
1793 ms
1368 ms
1795 ms
1518 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 42% of them (60 requests) were addressed to the original Lenoxx.com.br, 15% (21 requests) were made to Apis.google.com and 15% (21 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Lenoxx.com.br.
Page size can be reduced by 1.2 MB (33%)
3.5 MB
2.4 MB
In fact, the total size of Lenoxx.com.br main page is 3.5 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. 85% 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 2.3 MB which makes up the majority of the site volume.
Potential reduce by 83.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. 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 83.5 kB or 85% of the original size.
Potential reduce by 192.1 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. Lenoxx images are well optimized though.
Potential reduce by 436.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 436.9 kB or 74% of the original size.
Potential reduce by 446.0 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. Lenoxx.com.br needs all CSS files to be minified and compressed as it can save up to 446.0 kB or 79% of the original size.
Number of requests can be reduced by 98 (74%)
133
35
The browser has sent 133 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lenoxx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 51 to 1 for JavaScripts and from 31 to 1 for CSS and as a result speed up the page load time.
lenoxx.com.br
3278 ms
wp-emoji-release.min.js
1793 ms
validationEngine.jquery.css
1368 ms
tmw-start.css
1795 ms
normalize.css
1518 ms
font-awesome.css
6 ms
template.css
1543 ms
wp.css
1403 ms
stuff.css
1958 ms
wp.extensions.css
2088 ms
extensions.css
2383 ms
tmw-end.css
2386 ms
shortcodes.typography.css
2380 ms
shortcodes.elements.css
2089 ms
shortcodes.template.css
2231 ms
style1.css
2654 ms
override.css
2386 ms
thickbox.css
2658 ms
styles.css
2794 ms
page-list.css
2659 ms
dashicons.min.css
3362 ms
jquery.js
3638 ms
jquery-migrate.min.js
3356 ms
css
38 ms
css
52 ms
platform.js
71 ms
gk.scripts.js
3223 ms
shortcodes.typography.js
2663 ms
shortcodes.elements.js
2802 ms
shortcodes.template.js
2942 ms
thickbox.js
3550 ms
jquery.form.min.js
3710 ms
scripts.js
3788 ms
gk-nsp.js
3788 ms
thickbox.js
3915 ms
gk-tabs.js
4098 ms
wp-embed.min.js
3954 ms
gk.menu.js
4376 ms
tmw.js
4751 ms
jquery.validationEngine-pt.js
4465 ms
jquery.validationEngine.js
5043 ms
front-subscribers.js
3530 ms
icon.css
177 ms
css
14 ms
font-awesome.min.css
37 ms
css
58 ms
sac_logo_rodape.png
428 ms
PFR901-Principal.png
2120 ms
PMC451-Principal.png
2115 ms
PMP433-Principal.png
2832 ms
PTR201-Principal.png
2903 ms
PCA011-Principal.png
2838 ms
CA301-Principal.png
3185 ms
CA304-Principal.png
3831 ms
TB5500-Principal.png
3540 ms
BD1500-Principal.png
4140 ms
BD1501-Principal.png
4334 ms
AD2601-Principal.png
4240 ms
elretrolarshow2015.png
4574 ms
elretrolarshow.png
4930 ms
logo_rodape.png
559 ms
sdk.js
58 ms
logo.png
4241 ms
EkuTIhT2aGA
148 ms
logo_tmw1.png
4496 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
102 ms
0ihfXUL2emPh0ROJezvraKCWcynf_cDxXwCLxiixG1c.ttf
103 ms
fontawesome-webfont.woff
17 ms
fontawesome-webfont.woff
186 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
18 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
17 ms
2hig-tnMw8lXZsjwuh-9ow.ttf
19 ms
evC1haE-MsorTl_A7_uSGaCWcynf_cDxXwCLxiixG1c.ttf
18 ms
199 ms
m4miDWsenj8
163 ms
xd_arbiter.php
17 ms
xd_arbiter.php
1034 ms
www-embed-player-vflfNyN_r.css
36 ms
www-embed-player.js
58 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
86 ms
ad_status.js
61 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
41 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
44 ms
cb=gapi.loaded_0
48 ms
cb=gapi.loaded_1
46 ms
fastbutton
118 ms
fastbutton
115 ms
fastbutton
112 ms
fastbutton
152 ms
fastbutton
164 ms
fastbutton
155 ms
fastbutton
165 ms
fastbutton
158 ms
fastbutton
162 ms
fastbutton
381 ms
fastbutton
377 ms
fastbutton
370 ms
fastbutton
383 ms
loadingAnimation.gif
2904 ms
postmessageRelay
88 ms
rs=AGLTcCMZQMkD3nQb9neyXrDGlfp1IpCqrw
77 ms
3193398744-postmessagerelay.js
248 ms
rpc:shindig_random.js
239 ms
like.php
235 ms
cb=gapi.loaded_0
227 ms
cb=gapi.loaded_1
221 ms
fNFEOa8-9dh.js
114 ms
LVx-xkvaJ0b.png
78 ms
like.php
170 ms
like.php
275 ms
like.php
259 ms
like.php
272 ms
like.php
283 ms
like.php
232 ms
cb=gapi.loaded_0
19 ms
like.php
213 ms
like.php
283 ms
like.php
304 ms
like.php
304 ms
like.php
287 ms
like.php
310 ms
fNFEOa8-9dh.js
25 ms
fNFEOa8-9dh.js
12 ms
fNFEOa8-9dh.js
9 ms
fNFEOa8-9dh.js
64 ms
fNFEOa8-9dh.js
53 ms
fNFEOa8-9dh.js
47 ms
fNFEOa8-9dh.js
58 ms
fNFEOa8-9dh.js
57 ms
fNFEOa8-9dh.js
49 ms
fNFEOa8-9dh.js
44 ms
fNFEOa8-9dh.js
47 ms
fNFEOa8-9dh.js
96 ms
fNFEOa8-9dh.js
95 ms
fNFEOa8-9dh.js
90 ms
fNFEOa8-9dh.js
90 ms
fNFEOa8-9dh.js
90 ms
fNFEOa8-9dh.js
81 ms
fNFEOa8-9dh.js
74 ms
fNFEOa8-9dh.js
72 ms
desktop.small.css
277 ms
tablet.css
697 ms
tablet.small.css
551 ms
mobile.css
694 ms
lenoxx.com.br SEO score
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lenoxx.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Lenoxx.com.br 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.
lenoxx.com.br
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: