Tools & Wizards About Us
grozzr.ng screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

grozzr.ng

Home - Grozzr

Page Load Speed

3.2 sec in total

First Response

654 ms

Resources Loaded

1.4 sec

Page Rendered

1.1 sec

grozzr.ng screenshot

About Website

Visit grozzr.ng now to see the best up-to-date Grozzr content and also check out these interesting facts you probably never knew about grozzr.ng

Visit grozzr.ng

Key Findings

We analyzed Grozzr.ng page load time and found that the first response time was 654 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

grozzr.ng performance score

0

Network Requests Diagram

grozzr.ng

654 ms

bootstrap.min.css

166 ms

font-awesome.min.css

86 ms

et-line-font.css

60 ms

flexslider.css

62 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 75% of them (45 requests) were addressed to the original Grozzr.ng, 8% (5 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (654 ms) belongs to the original domain Grozzr.ng.

Page Optimization Overview & Recommendations

Page size can be reduced by 632.3 kB (25%)

Content Size

2.5 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-86%

Potential reduce by 33.0 kB

  • Original 38.2 kB
  • After minification 26.8 kB
  • After compression 5.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 11.4 kB, which is 30% 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 33.0 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 186.4 kB

  • Original 2.0 MB
  • After minification 1.8 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. Grozzr images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 176.9 kB

  • Original 258.3 kB
  • After minification 243.0 kB
  • After compression 81.4 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 176.9 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 236.0 kB

  • Original 277.2 kB
  • After minification 241.3 kB
  • After compression 41.2 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. Grozzr.ng needs all CSS files to be minified and compressed as it can save up to 236.0 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (39%)

Requests Now

51

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

grozzr.ng

grozzr.ng

654 ms

bootstrap.min.css

bootstrap.min.css

166 ms

font-awesome.min.css

font-awesome.min.css

86 ms

et-line-font.css

et-line-font.css

60 ms

flexslider.css

flexslider.css

62 ms

owl.carousel.css

owl.carousel.css

58 ms

animate.css

animate.css

189 ms

style.css

style.css

176 ms

reset.css

reset.css

120 ms

slider.css

slider.css

33 ms

css

css

24 ms

css

css

36 ms

css

css

44 ms

grozzr-white.png

grozzr-white.png

90 ms

grozzr.png

grozzr.png

107 ms

grozzr-groundnut.jpg

grozzr-groundnut.jpg

204 ms

grozzr-pigs.jpg

grozzr-pigs.jpg

199 ms

grozzr-banana.jpg

grozzr-banana.jpg

171 ms

preloader.gif

preloader.gif

154 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

6 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

26 ms

Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf

Zd2E9abXLFGSr9G3YK2MsMEHkXu385rSv8spHqOuvSI.ttf

25 ms

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

b9QBgL0iMZfDSpmcXcE8nPVE82mBoqAQeMZO1WdebIw.ttf

24 ms

Y_Jmwi-iHxNj27PG4ILsdSZ2oysoEQEeKwjgmXLRnTc.ttf

Y_Jmwi-iHxNj27PG4ILsdSZ2oysoEQEeKwjgmXLRnTc.ttf

24 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

129 ms

et-line.woff

et-line.woff

177 ms

lamb-451982_960_720.jpg

lamb-451982_960_720.jpg

5 ms

question-mark-460869_960_720.jpg

question-mark-460869_960_720.jpg

18 ms

behavior-change-expert-questions.jpg

behavior-change-expert-questions.jpg

16 ms

lamb-451982_960_720.jpg

lamb-451982_960_720.jpg

16 ms

bootstrap.min.js

bootstrap.min.js

88 ms

appear.js

appear.js

87 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

129 ms

smoothscroll.js

smoothscroll.js

89 ms

wow.min.js

wow.min.js

108 ms

owl.carousel.min.js

owl.carousel.min.js

146 ms

custom.js

custom.js

130 ms

question-mark-460869_960_720.jpg

question-mark-460869_960_720.jpg

10 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

210 ms

prev-light.png

prev-light.png

33 ms

next-light.png

next-light.png

33 ms

flexslider-icon.woff

flexslider-icon.woff

59 ms

defer.js

defer.js

58 ms

grozzr-milled-eguisi-2.jpg

grozzr-milled-eguisi-2.jpg

149 ms

grozzr-rice-unmilled-2.jpg

grozzr-rice-unmilled-2.jpg

122 ms

grozzr-cassava-1.jpg

grozzr-cassava-1.jpg

136 ms

grozzr-red-sorghum-1.jpg

grozzr-red-sorghum-1.jpg

173 ms

grozzr-white-maize-2.jpg

grozzr-white-maize-2.jpg

148 ms

grozzr-millet-1.jpg

grozzr-millet-1.jpg

174 ms

grozzr-oranges-4.jpg

grozzr-oranges-4.jpg

239 ms

grozzr-yam-220-to-240.jpg

grozzr-yam-220-to-240.jpg

220 ms

grozzr-eguisi-unpeeled-2.jpg

grozzr-eguisi-unpeeled-2.jpg

286 ms

grozzr-pigs-2.jpg

grozzr-pigs-2.jpg

236 ms

grozzr-white-sorghum-5.jpg

grozzr-white-sorghum-5.jpg

342 ms

grozzr-potatoes_vegetables_potato.jpg

grozzr-potatoes_vegetables_potato.jpg

292 ms

grozzr-ogoja-yam-grade-1-32k-to-42k.jpg

grozzr-ogoja-yam-grade-1-32k-to-42k.jpg

331 ms

grozzr-ginger-4.jpg

grozzr-ginger-4.jpg

372 ms

analytics.js

analytics.js

19 ms

Homepage_awesome.jpg

Homepage_awesome.jpg

367 ms

collect

collect

15 ms

SEO Factors

grozzr.ng SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

grozzr.ng

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