11 sec in total
519 ms
10.1 sec
450 ms
Click here to check amazing Quick content for Brazil. Otherwise, check out these important facts you probably never knew about quick.com.br
Contrate hoje mesmo a QUICK e tenha a melhor internet fibra óptica da região. Suporte 24h por dia. Conheça os planos residenciais e empres...
Visit quick.com.brWe analyzed Quick.com.br page load time and found that the first response time was 519 ms and then it took 10.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
quick.com.br performance score
name
value
score
weighting
Value3.5 s
34/100
10%
Value11.8 s
0/100
25%
Value6.4 s
40/100
10%
Value140 ms
96/100
30%
Value0.667
8/100
15%
Value8.0 s
43/100
10%
519 ms
1915 ms
287 ms
428 ms
36 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 83% of them (40 requests) were addressed to the original Quick.com.br, 6% (3 requests) were made to Ajax.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.4 sec) belongs to the original domain Quick.com.br.
Page size can be reduced by 228.8 kB (15%)
1.5 MB
1.3 MB
In fact, the total size of Quick.com.br main page is 1.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. 45% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 13.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 2.2 kB, which is 12% 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 13.8 kB or 75% of the original size.
Potential reduce by 118.8 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. Quick images are well optimized though.
Potential reduce by 72.5 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 72.5 kB or 53% of the original size.
Potential reduce by 23.7 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. Quick.com.br needs all CSS files to be minified and compressed as it can save up to 23.7 kB or 82% of the original size.
Number of requests can be reduced by 9 (29%)
31
22
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Quick. 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 from 4 to 1 for CSS and as a result speed up the page load time.
quick.com.br
519 ms
1915 ms
nivoslider4wp.css
287 ms
style.css
428 ms
jquery.min.js
36 ms
css
42 ms
slide.js
2197 ms
slides.min.jquery.js
2323 ms
scripts.js
2242 ms
jquery.validationEngine.js
714 ms
jquery.min.js
66 ms
jquery.fancybox-1.3.4.pack.js
579 ms
jquery.fancybox-1.3.4.css
569 ms
jquery.min.js
11 ms
jquery.cookie.js
2531 ms
jquery.ulightbox.js
2593 ms
jquery.ulightbox.css
2625 ms
jquery.nivo.slider.pack.js
2484 ms
ga.js
13 ms
__utm.gif
12 ms
background.png
984 ms
barra_login.png
296 ms
tab_l.png
2705 ms
tab_m.png
2761 ms
bt_open.png
2935 ms
bt_close.png
2963 ms
tab_r.png
2929 ms
logo.png
1126 ms
telefone.png
1273 ms
menu.png
1415 ms
banner1.png
4127 ms
loading.gif
2850 ms
36_o.png
3467 ms
35_o.png
3548 ms
fdn_centro.png
3351 ms
modelo.png
3355 ms
anatel.png
3104 ms
pttbr.png
3249 ms
unotel.png
3395 ms
mikrotik.png
3499 ms
Ubiquiti.png
3500 ms
bt_over.png1
5431 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
21 ms
IQHow_FEYlDC4Gzy_m8fcvEr6Hm6RMS0v1dtXsGir4g.ttf
22 ms
bt_segundavia.png
3577 ms
bg_rodape.png
4028 ms
menu_rodape.png
3611 ms
assinatura-brasmid.png
3661 ms
quick.com.br 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
Form elements do not have associated labels
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
quick.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
quick.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 doesn't use legible font sizes
PT
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Quick.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 Quick.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.
quick.com.br
Open Graph description is not detected on the main page of Quick. 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: