Tools & Wizards About Us
ifruitplanner.com.br screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

ifruitplanner.com.br

iFruit Planner

Page Load Speed

10.1 sec in total

First Response

737 ms

Resources Loaded

8.8 sec

Page Rendered

595 ms

ifruitplanner.com.br screenshot

About Website

Visit ifruitplanner.com.br now to see the best up-to-date IFruit Planner content and also check out these interesting facts you probably never knew about ifruitplanner.com.br

Visit ifruitplanner.com.br

Key Findings

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

Performance Metrics

ifruitplanner.com.br performance score

0

Network Requests Diagram

ifruitplanner.com.br

737 ms

css

123 ms

reset.css

198 ms

jquery-ui-1.10.4.custom.min.css

387 ms

sematic.css

1833 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 71% of them (27 requests) were addressed to the original Ifruitplanner.com.br, 8% (3 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (5.2 sec) belongs to the original domain Ifruitplanner.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 868.9 kB (76%)

Content Size

1.1 MB

After Optimization

280.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifruitplanner.com.br main page is 1.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. 40% of websites need less resources to load. Javascripts take 668.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 16.8 kB

  • Original 23.0 kB
  • After minification 20.2 kB
  • After compression 6.2 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.8 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 16.8 kB or 73% of the original size.

Image Optimization

-13%

Potential reduce by 8.0 kB

  • Original 61.9 kB
  • After minification 53.9 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. Obviously, IFruit Planner needs image optimization as it can save up to 8.0 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 493.8 kB

  • Original 668.3 kB
  • After minification 615.3 kB
  • After compression 174.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 493.8 kB or 74% of the original size.

CSS Optimization

-88%

Potential reduce by 350.4 kB

  • Original 396.4 kB
  • After minification 272.9 kB
  • After compression 46.0 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. Ifruitplanner.com.br needs all CSS files to be minified and compressed as it can save up to 350.4 kB or 88% of the original size.

Requests Breakdown

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

Requests Now

34

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifruitplanner.com.br

ifruitplanner.com.br

737 ms

css

css

123 ms

reset.css

reset.css

198 ms

jquery-ui-1.10.4.custom.min.css

jquery-ui-1.10.4.custom.min.css

387 ms

sematic.css

sematic.css

1833 ms

boxer.css

boxer.css

1171 ms

style.css

style.css

406 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

600 ms

jquery.lionbars.0.3.js

jquery.lionbars.0.3.js

1190 ms

modernizr-2.js

modernizr-2.js

568 ms

jquery-ui-1.10.4.custom.min.js

jquery-ui-1.10.4.custom.min.js

2458 ms

semantic-ui.js

semantic-ui.js

971 ms

boxer.js

boxer.js

798 ms

mascaras.js

mascaras.js

993 ms

custom.js

custom.js

1162 ms

jcycle.js

jcycle.js

1189 ms

analytics.js

analytics.js

130 ms

logo-ifruit.jpg

logo-ifruit.jpg

201 ms

bg-login.jpg

bg-login.jpg

1509 ms

bg-login-bto.jpg

bg-login-bto.jpg

201 ms

bg-caixa-fb.jpg

bg-caixa-fb.jpg

387 ms

facebook.png

facebook.png

202 ms

all.js

all.js

257 ms

bg-home-cadastro.jpg

bg-home-cadastro.jpg

201 ms

bto-criar-conta.jpg

bto-criar-conta.jpg

338 ms

banner.jpg

banner.jpg

4136 ms

bg-footer-home.jpg

bg-footer-home.jpg

5211 ms

ico-fb.png

ico-fb.png

383 ms

ico-in.png

ico-in.png

515 ms

up.png

up.png

534 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

149 ms

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf

201 ms

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf

307 ms

collect

collect

66 ms

258 ms

xd_arbiter.php

xd_arbiter.php

204 ms

xd_arbiter.php

xd_arbiter.php

415 ms

xd_arbiter.php

xd_arbiter.php

153 ms

SEO Factors

ifruitplanner.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 Ifruitplanner.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 Ifruitplanner.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

ifruitplanner.com.br

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