4.8 sec in total
466 ms
1.8 sec
2.5 sec
Click here to check amazing Grinna content. Otherwise, check out these important facts you probably never knew about grinna.org
Founder & CEO of EverTrue
Visit grinna.orgWe analyzed Grinna.org page load time and found that the first response time was 466 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster. This domain responded with an error, which can significantly jeopardize Grinna.org rating and web reputation
grinna.org performance score
466 ms
10 ms
35 ms
8 ms
29 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Grinna.org, 19% (12 requests) were made to Public.slidesharecdn.com and 16% (10 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (936 ms) relates to the external source 40.media.tumblr.com.
Page size can be reduced by 613.2 kB (13%)
4.6 MB
4.0 MB
In fact, the total size of Grinna.org main page is 4.6 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. 60% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 113.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. This page needs HTML code to be minified as it can gain 34.5 kB, which is 25% 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 113.3 kB or 82% of the original size.
Potential reduce by 101.6 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. Grinna images are well optimized though.
Potential reduce by 319.2 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 319.2 kB or 62% of the original size.
Potential reduce by 79.1 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. Grinna.org needs all CSS files to be minified and compressed as it can save up to 79.1 kB or 74% of the original size.
Number of requests can be reduced by 28 (47%)
60
32
The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Grinna. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
grinna.org
466 ms
pre_tumblelog.js
10 ms
reset.css
35 ms
tumblelog_post_message_queue.js
8 ms
stylesheet.css
29 ms
jquery-1.7.2.min.js
27 ms
index.js
28 ms
analytics.js
287 ms
avatar_b9b116624333_64.png
263 ms
tumblr_o3nvbksLo71snf7wlo1_1280.jpg
936 ms
like_iframe.html
272 ms
1dfa7f2.jpg
545 ms
17415022
542 ms
tumblr_inline_n1atn6tqls1s5h9ft.png
700 ms
tumblr_inline_n0590eTwSG1s5h9ft.png
389 ms
tumblr_mw00zfwJrI1scr119o1_1280.jpg
645 ms
impixu
478 ms
tumblr_o3t5tn90ZR1snf7wlo1_1280.jpg
861 ms
tumblr_mvwheohHzV1sijr9io1_1280.jpg
491 ms
tumblr_inline_n0593iDw2C1s5h9ft.png
181 ms
tumblr_inline_mzys2j2yW11s5h9ft.png
255 ms
2f5eb5f.jpg
297 ms
tumblr_inline_n058xsOnaT1s5h9ft.png
408 ms
tumblr_inline_n05915KOit1s5h9ft.png
297 ms
tumblr_inline_mzysa9n0yM1s5h9ft.png
490 ms
tumblr_inline_mvab8ozU6C1s5h9ft.jpg
400 ms
impixu
304 ms
tumblr_inline_n1b7jeYZgA1s5h9ft.png
175 ms
tumblr_inline_mzys5fd8lM1s5h9ft.png
200 ms
icons_sprite.png
46 ms
arrow_sprite.png
163 ms
analytics.html
182 ms
login_check.html
44 ms
collect
132 ms
avatar_b9b116624333_40.png
107 ms
iframe_logo.png
51 ms
rapid-3.36.js
126 ms
rapidworker-1.2.js
123 ms
combined_jquery.js
313 ms
global.js
312 ms
combined_li_tracking.js
293 ms
font-awesome.css
292 ms
combined_presentation.css
359 ms
combined_player_presentation.js
357 ms
combined_old_embed.js
350 ms
ga.js
183 ms
analytics.js
182 ms
cs.js
221 ms
yql
538 ms
__utm.gif
36 ms
combined_base.js
72 ms
beacon.js
63 ms
__utm.gif
218 ms
culture-code-creating-a-lovable-company-1-638.jpg
288 ms
1x1.gif
192 ms
logo_embed_20x20_v1.png
179 ms
17415022
181 ms
lead-form
178 ms
__utm.gif
40 ms
status
49 ms
fontawesome-webfont.woff
108 ms
icons.svg
78 ms
cedexis.radar.js
5 ms
grinna.org SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Grinna.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Grinna.org 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.
grinna.org
Open Graph data is detected on the main page of Grinna. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: