Tools & Wizards About Us
blinkr.net screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

blinkr.net

-_- – free images for your projects

Page Load Speed

2.8 sec in total

First Response

273 ms

Resources Loaded

2.1 sec

Page Rendered

394 ms

blinkr.net screenshot

About Website

Click here to check amazing Blinkr content for United States. Otherwise, check out these important facts you probably never knew about blinkr.net

design news stream Facebook @twitter

Visit blinkr.net

Key Findings

We analyzed Blinkr.net page load time and found that the first response time was 273 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

blinkr.net performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

blinkr.net

273 ms

designcorner.blinkr.net

404 ms

pre_tumblelog.js

7 ms

jquery-1.7.2.min.js

25 ms

stacky.js

59 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Blinkr.net, 23% (15 requests) were made to Assets.tumblr.com and 13% (8 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (632 ms) relates to the external source 45.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 520.2 kB (46%)

Content Size

1.1 MB

After Optimization

600.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Blinkr.net 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. 60% of websites need less resources to load. Javascripts take 694.8 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 40.7 kB

  • Original 52.2 kB
  • After minification 50.4 kB
  • After compression 11.5 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 40.7 kB or 78% of the original size.

Image Optimization

-10%

Potential reduce by 35.7 kB

  • Original 369.2 kB
  • After minification 333.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. Blinkr images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 440.4 kB

  • Original 694.8 kB
  • After minification 692.9 kB
  • After compression 254.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 440.4 kB or 63% of the original size.

CSS Optimization

-69%

Potential reduce by 3.4 kB

  • Original 5.0 kB
  • After minification 5.0 kB
  • After compression 1.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. Blinkr.net needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (51%)

Requests Now

61

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

blinkr.net

blinkr.net

273 ms

designcorner.blinkr.net

designcorner.blinkr.net

404 ms

pre_tumblelog.js

pre_tumblelog.js

7 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

25 ms

stacky.js

stacky.js

59 ms

easing.js

easing.js

59 ms

ut.js

ut.js

58 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

16 ms

widgets.js

widgets.js

17 ms

index.js

index.js

20 ms

dc.js

dc.js

278 ms

tumblr_o43i1qGACN1r3gwf4o1_250.jpg

tumblr_o43i1qGACN1r3gwf4o1_250.jpg

268 ms

tumblr_o42lgrsGIV1r3gwf4o1_250.jpg

tumblr_o42lgrsGIV1r3gwf4o1_250.jpg

269 ms

tumblr_o42lgnw3Sd1r3gwf4o1_250.jpg

tumblr_o42lgnw3Sd1r3gwf4o1_250.jpg

268 ms

tumblr_o4178hvKmF1r3gwf4o1_75sq.gif

tumblr_o4178hvKmF1r3gwf4o1_75sq.gif

262 ms

tumblr_o40pr8Ts761r3gwf4o1_250.gif

tumblr_o40pr8Ts761r3gwf4o1_250.gif

632 ms

impixu

impixu

329 ms

stacky2

stacky2

393 ms

button.0308b81ff1714e446f674b5b9793f2cd.js

button.0308b81ff1714e446f674b5b9793f2cd.js

432 ms

tumblr_o42lgmI3c11r3gwf4o1_250.jpg

tumblr_o42lgmI3c11r3gwf4o1_250.jpg

320 ms

tumblr_o42lgjPD9R1r3gwf4o1_250.jpg

tumblr_o42lgjPD9R1r3gwf4o1_250.jpg

388 ms

tumblr_o40prwSy841r3gwf4o1_250.jpg

tumblr_o40prwSy841r3gwf4o1_250.jpg

388 ms

tumblr_o409sdXV781r3gwf4o1_250.jpg

tumblr_o409sdXV781r3gwf4o1_250.jpg

391 ms

tumblr_o3zbq44tDx1r3gwf4o1_250.jpg

tumblr_o3zbq44tDx1r3gwf4o1_250.jpg

387 ms

tumblr_o3zbq4iOSV1r3gwf4o1_250.jpg

tumblr_o3zbq4iOSV1r3gwf4o1_250.jpg

386 ms

tumblr_o3zbq2fuem1r3gwf4o1_250.jpg

tumblr_o3zbq2fuem1r3gwf4o1_250.jpg

387 ms

impixu

impixu

319 ms

tumblr_o4178gPVSR1r3gwf4o1_75sq.gif

tumblr_o4178gPVSR1r3gwf4o1_75sq.gif

317 ms

bg2.jpg

bg2.jpg

114 ms

tumblr_static_designcorner.blinkr.net.png

tumblr_static_designcorner.blinkr.net.png

314 ms

footer.png

footer.png

108 ms

white-90perc-opacity.png

white-90perc-opacity.png

114 ms

tumblr_o42lgpaafu1r3gwf4o1_250.jpg

tumblr_o42lgpaafu1r3gwf4o1_250.jpg

113 ms

tumblr_o3zbq3SEBk1r3gwf4o1_250.jpg

tumblr_o3zbq3SEBk1r3gwf4o1_250.jpg

113 ms

analytics.html

analytics.html

530 ms

login_check.html

login_check.html

107 ms

__utm.gif

__utm.gif

283 ms

avatar_c1e764ebaa7f_40.png

avatar_c1e764ebaa7f_40.png

254 ms

iframe_logo.png

iframe_logo.png

221 ms

404.css

404.css

99 ms

errors.js

errors.js

85 ms

_t.js

_t.js

90 ms

error_page.js

error_page.js

165 ms

status.js

status.js

189 ms

iframe_sprite.png

iframe_sprite.png

375 ms

transparent-pixel.png

transparent-pixel.png

169 ms

logo_404.png

logo_404.png

113 ms

dashboard_controls_sprite.png

dashboard_controls_sprite.png

112 ms

ga.js

ga.js

126 ms

analytics.js

analytics.js

127 ms

rapid-3.36.js

rapid-3.36.js

125 ms

rapidworker-1.2.js

rapidworker-1.2.js

128 ms

avatar_f1bf2261caea_128.png

avatar_f1bf2261caea_128.png

202 ms

tumblr_mnh375KPGH1rk1qp5o1_500.gif

tumblr_mnh375KPGH1rk1qp5o1_500.gif

556 ms

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html

73 ms

__utm.gif

__utm.gif

56 ms

info.json

info.json

194 ms

ga.js

ga.js

140 ms

analytics.js

analytics.js

114 ms

cs.js

cs.js

111 ms

yql

yql

280 ms

__utm.gif

__utm.gif

23 ms

jot

jot

101 ms

cedexis.radar.js

cedexis.radar.js

8 ms

Accessibility Review

blinkr.net accessibility score

61

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

blinkr.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

blinkr.net SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blinkr.net 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 Blinkr.net 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

blinkr.net

Open Graph data is detected on the main page of Blinkr. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: