Tools & Wizards About Us
epicom.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

epicom.com.br

Hubsell – Tecnologia para Integração e Omnichannel

Page Load Speed

4.8 sec in total

First Response

599 ms

Resources Loaded

3.4 sec

Page Rendered

837 ms

epicom.com.br screenshot

About Website

Visit epicom.com.br now to see the best up-to-date Epicom content for Brazil and also check out these interesting facts you probably never knew about epicom.com.br

Marketplace agora é para você! É para sua loja!Sua vitrine muito mais completa e com incrível sortimento!

Visit epicom.com.br

Key Findings

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

Performance Metrics

epicom.com.br performance score

0

Network Requests Diagram

epicom.com.br

599 ms

css

44 ms

css

59 ms

bootstrap.css

740 ms

font-awesome.min.css

300 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 43% of them (45 requests) were addressed to the original Epicom.com.br, 32% (34 requests) were made to Maps.googleapis.com and 10% (10 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Epicom.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (29%)

Content Size

3.8 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Epicom.com.br main page is 3.8 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. Images take 2.5 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 45.3 kB

  • Original 53.5 kB
  • After minification 50.6 kB
  • After compression 8.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 45.3 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 133.1 kB

  • Original 2.5 MB
  • After minification 2.3 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. Epicom images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 546.0 kB

  • Original 822.7 kB
  • After minification 799.9 kB
  • After compression 276.7 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 546.0 kB or 66% of the original size.

CSS Optimization

-87%

Potential reduce by 369.7 kB

  • Original 425.3 kB
  • After minification 328.6 kB
  • After compression 55.6 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. Epicom.com.br needs all CSS files to be minified and compressed as it can save up to 369.7 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (47%)

Requests Now

92

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

epicom.com.br

epicom.com.br

599 ms

css

css

44 ms

css

css

59 ms

bootstrap.css

bootstrap.css

740 ms

font-awesome.min.css

font-awesome.min.css

300 ms

ionicons.min.css

ionicons.min.css

597 ms

liquid-slider.css

liquid-slider.css

308 ms

animate.css

animate.css

589 ms

YTPlayer.css

YTPlayer.css

299 ms

font-awesome.css

font-awesome.css

602 ms

cubeportfolio.css

cubeportfolio.css

894 ms

style.css

style.css

609 ms

blue.css

blue.css

742 ms

jquery.min.js

jquery.min.js

69 ms

bootstrap.min.js

bootstrap.min.js

763 ms

jquery.liquid-slider.js

jquery.liquid-slider.js

761 ms

jquery.stellar.js

jquery.stellar.js

775 ms

jquery.sticky.js

jquery.sticky.js

886 ms

waypoints.min.js

waypoints.min.js

888 ms

wow.min.js

wow.min.js

992 ms

jquery.counterup.min.js

jquery.counterup.min.js

992 ms

jquery.fitvids.js

jquery.fitvids.js

992 ms

modernizr.custom.js

modernizr.custom.js

1040 ms

toucheffects.js

toucheffects.js

1040 ms

jquery.easing.1.3.min.js

jquery.easing.1.3.min.js

1037 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

1061 ms

jquery.cubeportfolio.min.js

jquery.cubeportfolio.min.js

1222 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

1072 ms

jquery.mb.YTPlayer.js

jquery.mb.YTPlayer.js

1194 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

1189 ms

js

js

75 ms

gmap3.min.js

gmap3.min.js

1193 ms

scripts.js

scripts.js

1354 ms

logo.png

logo.png

1246 ms

slide-2.jpg

slide-2.jpg

1916 ms

slide-3.jpg

slide-3.jpg

2177 ms

client_logo1.png

client_logo1.png

1443 ms

client_logo2.png

client_logo2.png

1457 ms

client_logo3.png

client_logo3.png

1453 ms

hp-logo.png

hp-logo.png

1529 ms

client_logo10.png

client_logo10.png

1602 ms

client_logo5.png

client_logo5.png

1332 ms

client_logo6.png

client_logo6.png

1335 ms

ecomm.png

ecomm.png

1393 ms

preloader.gif

preloader.gif

1072 ms

pattern.png

pattern.png

865 ms

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

0DeoTBMnW4sOpD0Zb8OQSALUuEpTyoUstqEm5AMlJo4.ttf

11 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

16 ms

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

MZ1aViPqjfvZwVD_tzjjkwLUuEpTyoUstqEm5AMlJo4.ttf

18 ms

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

16 ms

Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf

Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf

17 ms

b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf

b9QBgL0iMZfDSpmcXcE8nBPtpc1JAjij63Hi_JcAPQ4.ttf

16 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1046 ms

common.js

common.js

29 ms

util.js

util.js

40 ms

geocoder.js

geocoder.js

40 ms

analytics.js

analytics.js

10 ms

slide-1.jpg

slide-1.jpg

1369 ms

collect

collect

29 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

264 ms

GeocodeService.Search

GeocodeService.Search

92 ms

collect

collect

58 ms

map.js

map.js

12 ms

marker.js

marker.js

52 ms

onion.js

onion.js

20 ms

openhand_8_8.cur

openhand_8_8.cur

56 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

101 ms

stats.js

stats.js

32 ms

controls.js

controls.js

40 ms

marker.png

marker.png

233 ms

transparent.png

transparent.png

35 ms

css

css

151 ms

google4.png

google4.png

53 ms

mapcnt6.png

mapcnt6.png

97 ms

sv5.png

sv5.png

125 ms

tmapctrl.png

tmapctrl.png

103 ms

cb_scout5.png

cb_scout5.png

133 ms

tmapctrl4.png

tmapctrl4.png

133 ms

imgs8.png

imgs8.png

132 ms

vt

vt

142 ms

vt

vt

147 ms

vt

vt

130 ms

vt

vt

156 ms

vt

vt

148 ms

vt

vt

157 ms

vt

vt

187 ms

vt

vt

167 ms

vt

vt

207 ms

vt

vt

191 ms

vt

vt

201 ms

vt

vt

215 ms

vt

vt

223 ms

vt

vt

230 ms

vt

vt

246 ms

vt

vt

255 ms

vt

vt

249 ms

vt

vt

272 ms

vt

vt

269 ms

vt

vt

263 ms

vt

vt

307 ms

vt

vt

312 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

42 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

61 ms

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf

83 ms

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf

83 ms

SEO Factors

epicom.com.br SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epicom.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Epicom.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

epicom.com.br

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