10.4 sec in total
737 ms
9.2 sec
506 ms
Visit lance.com.br now to see the best up-to-date LANCE content for Brazil and also check out these interesting facts you probably never knew about lance.com.br
LANCE! | Futebol, Vôlei, F-1, MMA e todos os esportes
Visit lance.com.brWe analyzed Lance.com.br page load time and found that the first response time was 737 ms and then it took 9.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.
lance.com.br performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value23.1 s
0/100
25%
Value22.6 s
0/100
10%
Value5,700 ms
0/100
30%
Value0.799
5/100
15%
Value51.9 s
0/100
10%
737 ms
49 ms
71 ms
391 ms
269 ms
Our browser made a total of 216 requests to load all elements on the main page. We found that 64% of them (138 requests) were addressed to the original Lance.com.br, 4% (8 requests) were made to Akfs.nspmotion.com and 3% (6 requests) were made to S.yimg.com. The less responsive or slowest element that took the longest time to load (6 sec) relates to the external source Clevernt.com.
Page size can be reduced by 3.0 MB (40%)
7.6 MB
4.5 MB
In fact, the total size of Lance.com.br main page is 7.6 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. 75% 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. Javascripts take 3.6 MB which makes up the majority of the site volume.
Potential reduce by 149.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 26.3 kB, which is 14% 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 149.5 kB or 81% of the original size.
Potential reduce by 176.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. LANCE images are well optimized though.
Potential reduce by 2.3 MB
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 2.3 MB or 64% of the original size.
Potential reduce by 423.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. Lance.com.br needs all CSS files to be minified and compressed as it can save up to 423.0 kB or 78% of the original size.
Number of requests can be reduced by 70 (36%)
192
122
The browser has sent 192 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LANCE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 54 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.lance.com.br
737 ms
publishertag.js
49 ms
gpt.js
71 ms
screen.css
391 ms
magnific-popup.css
269 ms
global.js
521 ms
0beb0b4.js
399 ms
addthis_widget.js
23 ms
OneSignalSDK.js
76 ms
count.js
30 ms
count.js
32 ms
pubads_impl_147.js
42 ms
container.html
9 ms
eplayer.js
344 ms
outbrain.js
52 ms
gtm.js
16 ms
profiles.js
79 ms
analytics.js
3 ms
hotjar-385418.js
22 ms
collect
5 ms
collect
53 ms
collect
3 ms
collect
69 ms
modules-f524bccd859bfc7e394e1123f7f90405.js
48 ms
profile
7 ms
59af122186ea2.jpeg
195 ms
59af120fb480c.jpeg
257 ms
59a88cebaf5cf.jpeg
257 ms
595291cc45bf6.jpeg
258 ms
59af2c0848be7.jpeg
260 ms
59af17f8202d7.jpeg
267 ms
59aebb29efdde.jpeg
404 ms
59356e1e12f4a.jpeg
511 ms
595e3c7d1072a.jpeg
512 ms
58b6e83747a6d.jpeg
515 ms
59af1f01c13cd.jpeg
516 ms
59aee256859d1.jpeg
522 ms
59af1cdae04a6.jpeg
649 ms
59add8462bb5b.jpeg
765 ms
59af1807735c3.jpeg
769 ms
59aee5a77ce8a.jpeg
769 ms
59af1bc1bf11e.jpeg
770 ms
59af1af43b473.jpeg
776 ms
59af17b154789.jpeg
902 ms
59af1a4e6afd0.jpeg
1024 ms
59af18b68ab26.jpeg
1023 ms
59a0506d29cd7.jpeg
1023 ms
59a1fa8aade34.jpeg
1025 ms
59af15cdb16f2.jpeg
1041 ms
5910dae7a829c.jpeg
1155 ms
59aee0ea26012.jpeg
1276 ms
59af0d4e244f6.jpeg
1276 ms
599f2505c6cef.jpeg
1285 ms
5899bf70b7b42.jpeg
1287 ms
59aeea8698c97.jpeg
1295 ms
59a8826094cb3.jpeg
1431 ms
599e25769955b.jpeg
1530 ms
59ab22629e756.jpeg
1531 ms
59addd34e4a3c.jpeg
1542 ms
58c7196449787.jpeg
1550 ms
59aeaf0d28b15.jpeg
1550 ms
gpt.js
20 ms
ads
885 ms
eplayer.html
251 ms
gemini.js
76 ms
_ate.track.config_resp
26 ms
300lo.json
56 ms
sh.48536d49e4da3bdba54606b4.html
56 ms
rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html
53 ms
1467 ms
beacon.js
41 ms
produto_lancecombr.js
276 ms
nobetaads&id=nolance.inter
527 ms
g-d-min.js
10 ms
ssi
122 ms
FjallaOne-Regular.woff
1661 ms
OpenSans.woff
1659 ms
OpenSans-Bold.woff
1687 ms
AlfaSlabOne-Regular.woff
1685 ms
AlfaSlabOne-Regular.woff
1680 ms
css
25 ms
ng-spieler.js
87 ms
cb-1495571992148-917.javascript
3 ms
68c013d4eec024d21b172ed0b862a9cc.jpeg
4 ms
1501170145276-658.jpg
11 ms
syndication.png
7 ms
Lato-Black.woff
1643 ms
send_data.js
178 ms
pixel.js
283 ms
OpenSans-ExtraBold.woff
1786 ms
OpenSans-Semibold.woff
2039 ms
OpenSans-BoldItalic.woff
1794 ms
561599568c34a.png
1676 ms
561599254ae9f.png
1670 ms
5615998f7804f.png
1659 ms
analytics.js
30 ms
561599b6b6446.png
1681 ms
px.gif
67 ms
561599fc275b1.png
1678 ms
56159a1a04dd5.png
1794 ms
56159a4c50e29.png
1793 ms
56159a6387097.png
1791 ms
56159a8104fab.png
1799 ms
osd.js
14 ms
main.min.js
117 ms
13584.js
136 ms
osd_listener.js
24 ms
57ee9e8a341ea40300ddbee4.cfg.js
157 ms
e9fab81daab9aa805e7f421b05b6a4e4.min.js
6045 ms
56159a9db4e26.png
1688 ms
56159abd5ce5e.png
1782 ms
58989c7ac92ad.png
1787 ms
59aed788e07f9.r_1504652662729.0-5-700-388.jpeg
2057 ms
5990a881203e8.jpeg
1896 ms
sync
96 ms
aep-formats-18.0.2.min.js
9 ms
57ee9e8a341ea40300ddbee4-1.tpl.min.js
22 ms
css
34 ms
lancenet-300x250.css
12 ms
596bc2f9b0737.jpeg
1945 ms
119 ms
ads.jsonp
156 ms
59af11f0cb140.jpeg
1831 ms
59aeea8698c97.jpeg
1783 ms
596bc2d03e240.jpeg
1781 ms
5899bf70b7b42.jpeg
2031 ms
59af1a4e6afd0.jpeg
2031 ms
undefined.png
29 ms
AVGE.png
17 ms
773873.jpg
17 ms
781255.jpg
21 ms
show_ads.js
5 ms
zrt_lookup.html
21 ms
show_ads_impl.js
31 ms
ads
208 ms
osd.js
18 ms
emily.html
106 ms
59a053977ff0f.jpeg
1889 ms
599f2505c6cef.jpeg
1806 ms
59aeff934390f.jpeg
1823 ms
59a41dab25c35.jpeg
1816 ms
59aebbf34f5d5.r_1504652616740.0-477-700-884.jpeg
2151 ms
57b5b6801f4f1.jpeg
2027 ms
css
12 ms
css
16 ms
style.css
1919 ms
nolancep.png
359 ms
propaganda&id=nolance.inter
90 ms
tm38259.js
24 ms
usr
92 ms
container.html
10 ms
ads
150 ms
slick.css
1677 ms
jquery-1.11.0.min.js
1839 ms
jquery-migrate-1.2.1.min.js
1683 ms
slick.min.js
1889 ms
placar.min.js
1895 ms
req
44 ms
pixel
13 ms
sync
86 ms
sync
102 ms
59a0506d29cd7.jpeg
1792 ms
59a987251b2f0.r_1504652616772.0-205-700-612.jpeg
1690 ms
593db85803dd5.jpeg
1764 ms
59a8d37b72b30.jpeg
1835 ms
59ade4ab64d75.jpeg
1781 ms
56b34ac48fbe4.jpeg
1746 ms
59af020a222ee.jpeg
1653 ms
59aeeee382408.jpeg
1692 ms
59a1b952d29d3.jpeg
1649 ms
59aec7d855dd3.jpeg
1779 ms
59adbbd724ad7.jpeg
1783 ms
59adb13601632.jpeg
1757 ms
59aeb34b5536f.r_1504652616928.246-0-666-500.jpeg
1693 ms
58cb0191e6ac7.jpeg
1805 ms
5994888ca8d8a.r_1504280216907.0-145-700-560.jpeg
1786 ms
59a977a5c0a6c.jpeg
1916 ms
594be33837a87.jpeg
1797 ms
59a03befda5c2.r_1504280216856.0-18-700-433.jpeg
1670 ms
598485a45de6d.r_1504280216899.0-29-700-444.jpeg
1708 ms
59a977a5c0a6c.jpeg
1691 ms
598485a45de6d.jpeg
1749 ms
59a03befda5c2.jpeg
1872 ms
599eee5b0c7b8.jpeg
1669 ms
5994888ca8d8a.jpeg
1675 ms
navigation-logo.png
1699 ms
arrow-down-green.png
1695 ms
header-menu-shadow.png
1748 ms
arrow-right-white.png
1877 ms
twitter-icon-green.png
1674 ms
facebook-icon-green.png
1669 ms
green.png
1690 ms
comments-icon-white.png
1671 ms
share-icon-white.png
1654 ms
icon-slider.png
1716 ms
shadow.png
1801 ms
comments-icon-grey.png
1645 ms
share-icon-grey.png
1679 ms
green-small.png
1672 ms
logo-ltv.png
1653 ms
arrow-right-black-big.png
1667 ms
arrow-left-white-slider.png
1680 ms
arrow-right-white-slider.png
1703 ms
blogs.png
1681 ms
facebook-footer.png
1724 ms
twitter-footer.png
1680 ms
youtube-footer.png
1666 ms
instagram-footer.png
1687 ms
arrow-down-green-big.png
1706 ms
small.png
1678 ms
20170822_60razoes_1600x900_lance_mrv_2208.jpg
1849 ms
argentina.png
1554 ms
venezuela.png
1540 ms
paraguai.png
1569 ms
uruguai.png
1591 ms
footstats.png
1559 ms
lance.com.br accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
lance.com.br 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
lance.com.br 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
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lance.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Lance.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.
lance.com.br
Open Graph data is detected on the main page of LANCE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: