Tools & Wizards About Us
currante.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

currante.com

currantes.com ahora es beBee, Affinity Networking

Page Load Speed

2 sec in total

First Response

343 ms

Resources Loaded

1.4 sec

Page Rendered

195 ms

currante.com screenshot

About Website

Welcome to currante.com homepage info - get ready to check Currante best content right away, or after learning these important things about currante.com

Miles de currantes te están esperando en beBee. currantes.com ahora es la nueva red de Affinity Networking

Visit currante.com

Key Findings

We analyzed Currante.com page load time and found that the first response time was 343 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

currante.com performance score

0

Network Requests Diagram

currante.com

343 ms

currantes.com

305 ms

bootstrap.min.css

216 ms

landing.css

202 ms

verticales2.css

211 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Currante.com, 26% (7 requests) were made to Currantes.com and 15% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (525 ms) relates to the external source Currantes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 160.2 kB (50%)

Content Size

321.0 kB

After Optimization

160.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Currante.com main page is 321.0 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. CSS take 142.0 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 6.0 kB

  • Original 9.0 kB
  • After minification 8.6 kB
  • After compression 3.1 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 6.0 kB or 66% of the original size.

Image Optimization

-3%

Potential reduce by 3.7 kB

  • Original 116.1 kB
  • After minification 112.4 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. Currante images are well optimized though.

JavaScript Optimization

-59%

Potential reduce by 32.0 kB

  • Original 53.8 kB
  • After minification 53.8 kB
  • After compression 21.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 32.0 kB or 59% of the original size.

CSS Optimization

-83%

Potential reduce by 118.5 kB

  • Original 142.0 kB
  • After minification 136.1 kB
  • After compression 23.5 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. Currante.com needs all CSS files to be minified and compressed as it can save up to 118.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (44%)

Requests Now

18

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

currante.com

currante.com

343 ms

currantes.com

currantes.com

305 ms

bootstrap.min.css

bootstrap.min.css

216 ms

landing.css

landing.css

202 ms

verticales2.css

verticales2.css

211 ms

css

css

22 ms

css

css

35 ms

gtm.js

gtm.js

38 ms

logo-error.png

logo-error.png

108 ms

oficios.jpg

oficios.jpg

525 ms

bee150.png

bee150.png

100 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

8 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

11 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

14 ms

nj47mAZe0mYUIySgfn0wpQ.ttf

nj47mAZe0mYUIySgfn0wpQ.ttf

15 ms

analytics.js

analytics.js

7 ms

conversion_async.js

conversion_async.js

16 ms

fbevents.js

fbevents.js

82 ms

linkid.js

linkid.js

5 ms

collect

collect

6 ms

collect

collect

54 ms

33 ms

collect

collect

45 ms

83 ms

ga-audiences

ga-audiences

70 ms

ga-audiences

ga-audiences

68 ms

19 ms

SEO Factors

currante.com SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

currante.com

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