Tools & Wizards About Us
refrigerantespureza.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

refrigerantespureza.com

Refrigerantes Pureza

Page Load Speed

6.3 sec in total

First Response

474 ms

Resources Loaded

4.6 sec

Page Rendered

1.3 sec

refrigerantespureza.com screenshot

About Website

Visit refrigerantespureza.com now to see the best up-to-date Refrigerantes Pureza content and also check out these interesting facts you probably never knew about refrigerantespureza.com

Há mais de um século, a Pureza® fabrica os seus famosos refrigerantes e conquista gerações. Inspirada na pureza das águas límpidas da Serra Catarinense, da

Visit refrigerantespureza.com

Key Findings

We analyzed Refrigerantespureza.com page load time and found that the first response time was 474 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

refrigerantespureza.com performance score

0

Network Requests Diagram

refrigerantespureza.com

474 ms

refrigerantespureza.com.br

546 ms

M9QvL9AtSExPzUssy9SHMXSTi4t1DPQLSotSqxL1gRz9otTi1BJUoeLs1JzUkvw8VNG0xLzkyqT8CoRocUllTioA.css

147 ms

respond.js

293 ms

less.js

417 ms

Our browser made a total of 127 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Refrigerantespureza.com, 61% (77 requests) were made to Refrigerantespureza.com.br and 25% (32 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Refrigerantespureza.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (24%)

Content Size

5.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Refrigerantespureza.com main page is 5.1 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. 80% 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 3.9 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 122.7 kB

  • Original 142.0 kB
  • After minification 142.0 kB
  • After compression 19.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 122.7 kB or 86% of the original size.

Image Optimization

-9%

Potential reduce by 362.2 kB

  • Original 3.9 MB
  • After minification 3.5 MB

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. Refrigerantes Pureza images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 669.4 kB

  • Original 977.2 kB
  • After minification 941.6 kB
  • After compression 307.8 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 669.4 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 40.3 kB

  • Original 48.7 kB
  • After minification 47.6 kB
  • After compression 8.4 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. Refrigerantespureza.com needs all CSS files to be minified and compressed as it can save up to 40.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (34%)

Requests Now

119

After Optimization

79

  • Images
  • JavaScript
  • CSS

The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Refrigerantes Pureza. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

refrigerantespureza.com

refrigerantespureza.com

474 ms

refrigerantespureza.com.br

refrigerantespureza.com.br

546 ms

M9QvL9AtSExPzUssy9SHMXSTi4t1DPQLSotSqxL1gRz9otTi1BJUoeLs1JzUkvw8VNG0xLzkyqT8CoRocUllTioA.css

M9QvL9AtSExPzUssy9SHMXSTi4t1DPQLSotSqxL1gRz9otTi1BJUoeLs1JzUkvw8VNG0xLzkyqT8CoRocUllTioA.css

147 ms

respond.js

respond.js

293 ms

less.js

less.js

417 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

11 ms

send.form.script.js

send.form.script.js

297 ms

jquery-ui.js

jquery-ui.js

1568 ms

browser.js

browser.js

294 ms

waypoints.js

waypoints.js

292 ms

sequence.js

sequence.js

411 ms

imagesloaded.js

imagesloaded.js

1559 ms

quicksand.js

quicksand.js

1555 ms

hoverdir.js

hoverdir.js

1555 ms

fancybox.js

fancybox.js

1556 ms

page.js

page.js

1556 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

1396 ms

logo.png

logo.png

1387 ms

01.jpg

01.jpg

1384 ms

02.jpg

02.jpg

1389 ms

03.jpg

03.jpg

1385 ms

04.jpg

04.jpg

1387 ms

01.jpg

01.jpg

1391 ms

02.jpg

02.jpg

1389 ms

03.jpg

03.jpg

1412 ms

04.jpg

04.jpg

1414 ms

01.jpg

01.jpg

1414 ms

02.jpg

02.jpg

1417 ms

03.jpg

03.jpg

1414 ms

04.jpg

04.jpg

1419 ms

05.jpg

05.jpg

1417 ms

06.jpg

06.jpg

1417 ms

07.jpg

07.jpg

1420 ms

08.jpg

08.jpg

1826 ms

09.jpg

09.jpg

1486 ms

01.jpg

01.jpg

1486 ms

02.jpg

02.jpg

1829 ms

03.jpg

03.jpg

1420 ms

04.jpg

04.jpg

1826 ms

05.jpg

05.jpg

1831 ms

06.jpg

06.jpg

1728 ms

07.jpg

07.jpg

1735 ms

08.jpg

08.jpg

1752 ms

avantgarde.woff

avantgarde.woff

1740 ms

textbook.woff

textbook.woff

1630 ms

09.jpg

09.jpg

552 ms

10.jpg

10.jpg

548 ms

11.jpg

11.jpg

535 ms

12.jpg

12.jpg

682 ms

13.jpg

13.jpg

538 ms

14.jpg

14.jpg

763 ms

15.jpg

15.jpg

805 ms

16.jpg

16.jpg

754 ms

17.jpg

17.jpg

898 ms

18.jpg

18.jpg

753 ms

background.png

background.png

800 ms

preloader.gif

preloader.gif

898 ms

top_normal.png

top_normal.png

896 ms

top_hover.png

top_hover.png

896 ms

scroll.png

scroll.png

984 ms

left_big.png

left_big.png

982 ms

right_big.png

right_big.png

981 ms

left_small.png

left_small.png

980 ms

right_small.png

right_small.png

979 ms

analytics.js

analytics.js

318 ms

hover.png

hover.png

677 ms

jsapi

jsapi

103 ms

05.jpg

05.jpg

1014 ms

01.jpg

01.jpg

1392 ms

03.jpg

03.jpg

1107 ms

background.jpg

background.jpg

1093 ms

sabores.jpg

sabores.jpg

959 ms

background.jpg

background.jpg

1232 ms

background.jpg

background.jpg

1511 ms

fixed.gif

fixed.gif

1148 ms

more.png

more.png

1222 ms

twitter_normal.png

twitter_normal.png

1232 ms

twitter_hover.png

twitter_hover.png

1284 ms

facebook_normal.png

facebook_normal.png

1354 ms

facebook_hover.png

facebook_hover.png

1358 ms

collect

collect

22 ms

js

js

41 ms

common.js

common.js

27 ms

map.js

map.js

54 ms

util.js

util.js

53 ms

marker.js

marker.js

52 ms

onion.js

onion.js

64 ms

openhand_8_8.cur

openhand_8_8.cur

95 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

133 ms

stats.js

stats.js

35 ms

controls.js

controls.js

26 ms

transparent.png

transparent.png

56 ms

css

css

158 ms

google4.png

google4.png

65 ms

marker.png

marker.png

168 ms

mapcnt6.png

mapcnt6.png

66 ms

sv5.png

sv5.png

79 ms

vt

vt

104 ms

vt

vt

93 ms

vt

vt

92 ms

vt

vt

92 ms

vt

vt

114 ms

vt

vt

114 ms

vt

vt

120 ms

vt

vt

119 ms

vt

vt

119 ms

vt

vt

120 ms

vt

vt

139 ms

vt

vt

138 ms

vt

vt

138 ms

vt

vt

138 ms

vt

vt

138 ms

vt

vt

137 ms

vt

vt

203 ms

vt

vt

205 ms

vt

vt

203 ms

vt

vt

204 ms

vt

vt

202 ms

vt

vt

202 ms

tmapctrl.png

tmapctrl.png

87 ms

cb_scout5.png

cb_scout5.png

93 ms

tmapctrl4.png

tmapctrl4.png

109 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

74 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

98 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

140 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

140 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

271 ms

SEO Factors

refrigerantespureza.com SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Refrigerantespureza.com 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 Refrigerantespureza.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.

Social Sharing Optimization

refrigerantespureza.com

Open Graph description is not detected on the main page of Refrigerantes Pureza. 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: