Tools & Wizards About Us
pisantemercurius.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

pisantemercurius.com.br

Pisante Mercurius - Aqui você sabe aonde coloca os pés

Page Load Speed

11.4 sec in total

First Response

4.6 sec

Resources Loaded

6.3 sec

Page Rendered

530 ms

pisantemercurius.com.br screenshot

About Website

Welcome to pisantemercurius.com.br homepage info - get ready to check Pisante Mercurius best content right away, or after learning these important things about pisantemercurius.com.br

Pisante Mercurius

Visit pisantemercurius.com.br

Key Findings

We analyzed Pisantemercurius.com.br page load time and found that the first response time was 4.6 sec and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

pisantemercurius.com.br performance score

0

Network Requests Diagram

www.pisantemercurius.com.br

4600 ms

css

81 ms

css

93 ms

bootstrap.css

82 ms

bootstrap-theme.css

46 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 84% of them (90 requests) were addressed to the original Pisantemercurius.com.br, 9% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Pisantemercurius.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.2 MB (60%)

Content Size

3.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pisantemercurius.com.br main page is 3.7 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. 70% of websites need less resources to load. Javascripts take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 245.1 kB

  • Original 278.0 kB
  • After minification 236.9 kB
  • After compression 32.9 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 41.1 kB, which is 15% 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 245.1 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 47.5 kB

  • Original 923.8 kB
  • After minification 876.3 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. Pisante Mercurius images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 1.5 MB

  • Original 2.0 MB
  • After minification 1.6 MB
  • After compression 510.3 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 1.5 MB or 75% of the original size.

CSS Optimization

-86%

Potential reduce by 410.9 kB

  • Original 477.8 kB
  • After minification 375.8 kB
  • After compression 66.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. Pisantemercurius.com.br needs all CSS files to be minified and compressed as it can save up to 410.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 69 (73%)

Requests Now

95

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.pisantemercurius.com.br

www.pisantemercurius.com.br

4600 ms

css

css

81 ms

css

css

93 ms

bootstrap.css

bootstrap.css

82 ms

bootstrap-theme.css

bootstrap-theme.css

46 ms

font-awesome.min.css

font-awesome.min.css

53 ms

styles.css

styles.css

94 ms

widgets.css

widgets.css

42 ms

jquery.fancybox.css

jquery.fancybox.css

47 ms

owl.carousel.css

owl.carousel.css

58 ms

custommenu.css

custommenu.css

56 ms

effect.css

effect.css

66 ms

jquery-ui.css

jquery-ui.css

68 ms

ma_quickview.css

ma_quickview.css

63 ms

skin.css

skin.css

62 ms

ma.verticalmenu.css

ma.verticalmenu.css

82 ms

default.css

default.css

81 ms

mirasvit_searchindex.css

mirasvit_searchindex.css

72 ms

mirasvit_seo.css

mirasvit_seo.css

85 ms

sitemap.css

sitemap.css

82 ms

amconf.css

amconf.css

80 ms

tooltipster.css

tooltipster.css

85 ms

ma.banner7.css

ma.banner7.css

85 ms

animate.css

animate.css

113 ms

newsletter.css

newsletter.css

105 ms

prototype.js

prototype.js

169 ms

ccard.js

ccard.js

92 ms

validation.js

validation.js

96 ms

builder.js

builder.js

92 ms

effects.js

effects.js

102 ms

dragdrop.js

dragdrop.js

100 ms

controls.js

controls.js

129 ms

slider.js

slider.js

126 ms

js.js

js.js

127 ms

form.js

form.js

124 ms

menu.js

menu.js

129 ms

translate.js

translate.js

128 ms

cookies.js

cookies.js

133 ms

addthis_widget.js

addthis_widget.js

56 ms

ma.jq.slide.js

ma.jq.slide.js

176 ms

ajax_cart_super.js

ajax_cart_super.js

117 ms

ma.bxslider.min.js

ma.bxslider.min.js

112 ms

owl.carousel.js

owl.carousel.js

114 ms

ma.nivo.js

ma.nivo.js

103 ms

jquery-ui.js

jquery-ui.js

236 ms

bootstrap.js

bootstrap.js

150 ms

ma.mobilemenu.js

ma.mobilemenu.js

103 ms

backtotop.js

backtotop.js

143 ms

iwd-jquery-2.1.3.min.js

iwd-jquery-2.1.3.min.js

162 ms

modal.js

modal.js

137 ms

jquery.fancybox.js

jquery.fancybox.js

136 ms

custommenu.js

custommenu.js

127 ms

ma_quickview.js

ma_quickview.js

127 ms

ma.dropdown.js

ma.dropdown.js

142 ms

ma.accordion.js

ma.accordion.js

145 ms

jquery.min.js

jquery.min.js

158 ms

underscore.js

underscore.js

140 ms

backbone.js

backbone.js

140 ms

form.js

form.js

142 ms

autocomplete.js

autocomplete.js

134 ms

product.js

product.js

135 ms

configurable.js

configurable.js

136 ms

ma.flexslider.js

ma.flexslider.js

148 ms

jquery.bpopup.min.js

jquery.bpopup.min.js

141 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

150 ms

jquery-1.9.1.min.js

jquery-1.9.1.min.js

169 ms

formList.js

formList.js

135 ms

configurableList.js

configurableList.js

129 ms

jquery.tooltipster.min.js

jquery.tooltipster.min.js

131 ms

analytics.js

analytics.js

96 ms

pattern20.png

pattern20.png

62 ms

logo.png

logo.png

62 ms

loader.gif

loader.gif

58 ms

img_menu_1_.jpg

img_menu_1_.jpg

55 ms

slide1.jpg

slide1.jpg

62 ms

slide2.jpg

slide2.jpg

40 ms

slide3.jpg

slide3.jpg

111 ms

banner-glass1.jpg

banner-glass1.jpg

24 ms

banner-glass23.jpg

banner-glass23.jpg

35 ms

banner-glass3.jpg

banner-glass3.jpg

36 ms

banner-right.jpg

banner-right.jpg

40 ms

11-500x500.jpg

11-500x500.jpg

62 ms

10-500x500.jpg

10-500x500.jpg

103 ms

9-500x500.jpg

9-500x500.jpg

102 ms

payment.png

payment.png

102 ms

ajax-loader_1.gif

ajax-loader_1.gif

102 ms

loader_2.gif

loader_2.gif

102 ms

IczWvq5y_Cwwv_rBjOtT0w.woff

IczWvq5y_Cwwv_rBjOtT0w.woff

39 ms

CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff

CcKI4k9un7TZVWzRVT-T8xsxEYwM7FgeyaSgU71cLG0.woff

60 ms

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

-_Ctzj9b56b8RgXW8FAriRsxEYwM7FgeyaSgU71cLG0.woff

108 ms

8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff

8KhZd3VQBtXTAznvKjw-kxsxEYwM7FgeyaSgU71cLG0.woff

108 ms

xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff

xkvoNo9fC8O2RDydKj12bxsxEYwM7FgeyaSgU71cLG0.woff

108 ms

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

JbtMzqLaYbbbCL9X6EvaIxsxEYwM7FgeyaSgU71cLG0.woff

108 ms

1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff

1ImRNPx4870-D9a1EBUdPBsxEYwM7FgeyaSgU71cLG0.woff

109 ms

qLBu5CQmSMt1H43OiWJ77T8E0i7KZn-EPnyo3HZu7kw.woff

qLBu5CQmSMt1H43OiWJ77T8E0i7KZn-EPnyo3HZu7kw.woff

109 ms

r_tUZNl0G8xCoOmp_JkSCnhCUOGz7vYGh680lGh-uXM.woff

r_tUZNl0G8xCoOmp_JkSCnhCUOGz7vYGh680lGh-uXM.woff

108 ms

fND5XPYKrF2tQDwwfWZJI3hCUOGz7vYGh680lGh-uXM.woff

fND5XPYKrF2tQDwwfWZJI3hCUOGz7vYGh680lGh-uXM.woff

108 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

142 ms

loader.gif

loader.gif

107 ms

bkg_rating.png

bkg_rating.png

92 ms

collect

collect

96 ms

print.css

print.css

5 ms

bg-li.gif

bg-li.gif

15 ms

Newsletter_03_2.jpg

Newsletter_03_2.jpg

102 ms

300lo.json

300lo.json

48 ms

validation_advice_bg.gif

validation_advice_bg.gif

42 ms

sh.8e5f85691f9aaa082472a194.html

sh.8e5f85691f9aaa082472a194.html

41 ms

SEO Factors

pisantemercurius.com.br 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 Pisantemercurius.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 Pisantemercurius.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.

Social Sharing Optimization

pisantemercurius.com.br

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