2.3 sec in total
305 ms
1.8 sec
131 ms
Visit blog.count.ly now to see the best up-to-date Blog Count content for United States and also check out these interesting facts you probably never knew about blog.count.ly
Get both the most comprehensive product analytics platform needed to build outstanding and innovative products and the most privacy-conscious solution for mobile, desktop, and web applications. Create...
Visit blog.count.lyWe analyzed Blog.count.ly page load time and found that the first response time was 305 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
blog.count.ly performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value8.3 s
2/100
25%
Value6.1 s
45/100
10%
Value780 ms
38/100
30%
Value0
100/100
15%
Value11.4 s
19/100
10%
305 ms
44 ms
52 ms
53 ms
60 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Blog.count.ly, 25% (13 requests) were made to Static.tumblr.com and 15% (8 requests) were made to Assets.tumblr.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source 36.media.tumblr.com.
Page size can be reduced by 734.4 kB (43%)
1.7 MB
958.5 kB
In fact, the total size of Blog.count.ly main page is 1.7 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 926.6 kB which makes up the majority of the site volume.
Potential reduce by 65.4 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 65.4 kB or 72% of the original size.
Potential reduce by 249.5 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, Blog Count needs image optimization as it can save up to 249.5 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 360.9 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 360.9 kB or 60% of the original size.
Potential reduce by 58.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. Blog.count.ly needs all CSS files to be minified and compressed as it can save up to 58.6 kB or 82% of the original size.
Number of requests can be reduced by 21 (43%)
49
28
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Blog Count. 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 as a result speed up the page load time.
blog.count.ly
305 ms
pre_tumblelog.js
44 ms
jquery.fancybox-1.3.1.css
52 ms
style.css
53 ms
modernizr.2.6.1.min.js
60 ms
tumblelog_post_message_queue.js
41 ms
stylesheet.css
40 ms
tweets.js
293 ms
jquery.min.js
75 ms
script.js
43 ms
widgets.js
6 ms
plusone.js
118 ms
index.js
72 ms
tumblr_inline_o33thfTcrQ1rnfu3u_500.png
151 ms
tumblr_inline_o33tmfMfzk1rnfu3u_500.png
215 ms
tumblr_inline_o33to0Cm331rnfu3u_500.png
142 ms
tumblr_inline_o33u10tSQn1rnfu3u_500.png
199 ms
tumblr_inline_o2hm0qCy3v1rnfu3u_500.png
337 ms
tumblr_inline_o0ucvxr88X1rnfu3u_500.png
395 ms
tumblr_inline_o2hm0ccY5n1rnfu3u_500.png
197 ms
tumblr_inline_o26vyqAcdS1rnfu3u_500.png
1450 ms
background.png
58 ms
tumblr_static_untitled-1.fw.png
71 ms
effector-sprite.png
13 ms
post_shadow.png
10 ms
tumblr_static_untitled-2.fw.png
98 ms
social-icons-black.png
30 ms
tumblr_inline_o2hm31s7ga1rnfu3u_500.png
134 ms
tumblr_inline_o2hlyokfPv1rnfu3u_500.png
129 ms
tumblr_inline_o2hlzeP3cL1rnfu3u_500.png
194 ms
tumblr_inline_o0uei6cT4Q1rnfu3u_500.png
128 ms
header_shadow.png
101 ms
cb=gapi.loaded_0
84 ms
ga.js
83 ms
topbar_bg.png
80 ms
photo_btns_med.png
79 ms
impixu
126 ms
get_num_replies.js
187 ms
impixu
51 ms
analytics.html
305 ms
login_check.html
40 ms
__utm.gif
12 ms
collect
53 ms
ga-audiences
470 ms
rapid-3.33.js
60 ms
rapidworker-1.2.js
60 ms
ga.js
84 ms
analytics.js
70 ms
cs.js
45 ms
yql
239 ms
__utm.gif
11 ms
cedexis.radar.js
6 ms
blog.count.ly accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Image elements do not have [alt] attributes
blog.count.ly best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
blog.count.ly SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blog.count.ly 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 Blog.count.ly 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.
blog.count.ly
Open Graph data is detected on the main page of Blog Count. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: