1.9 sec in total
294 ms
927 ms
705 ms
Visit fishink.us now to see the best up-to-date Fishink content and also check out these interesting facts you probably never knew about fishink.us
Analysing the world through FISH EYE!!
Visit fishink.usWe analyzed Fishink.us page load time and found that the first response time was 294 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
fishink.us performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value5.7 s
16/100
25%
Value5.9 s
48/100
10%
Value780 ms
38/100
30%
Value0.293
41/100
15%
Value5.5 s
71/100
10%
294 ms
14 ms
27 ms
38 ms
9 ms
Our browser made a total of 46 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Fishink.us, 24% (11 requests) were made to Assets.tumblr.com and 9% (4 requests) were made to 41.media.tumblr.com. The less responsive or slowest element that took the longest time to load (582 ms) relates to the external source 49.media.tumblr.com.
Page size can be reduced by 381.8 kB (26%)
1.5 MB
1.1 MB
In fact, the total size of Fishink.us main page is 1.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. 50% of websites need less resources to load. Images take 947.2 kB which makes up the majority of the site volume.
Potential reduce by 35.0 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 35.0 kB or 76% of the original size.
Potential reduce by 24.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. Fishink images are well optimized though.
Potential reduce by 322.0 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 322.0 kB or 65% of the original size.
Potential reduce by 384 B
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. Fishink.us needs all CSS files to be minified and compressed as it can save up to 384 B or 59% of the original size.
Number of requests can be reduced by 9 (22%)
41
32
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fishink. 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 as a result speed up the page load time.
fishink.us
294 ms
pre_tumblelog.js
14 ms
css
27 ms
css
38 ms
tumblrautopager.js
9 ms
tumblelog_post_message_queue.js
24 ms
stylesheet.css
9 ms
index.js
24 ms
x.gif
13 ms
fishink.us
21 ms
avatar_f97ef92f7e22_30.png
13 ms
avatar_c108a4fc0fc7_30.png
20 ms
avatar_9cb4aa7b8fdd_30.png
71 ms
tumblr_o165caqJi31shohxho1_500.png
25 ms
tumblr_o0l15md21B1shohxho1_500.jpg
117 ms
tumblr_nmeqp4Mywc1s33dtio1_500.jpg
383 ms
tumblr_njlv8rJmIa1shohxho1_500.gif
582 ms
athenability_badge.png
10 ms
pyramid_closed_96.png
17 ms
tumblr_nyn123rY2T1shohxho1_500.jpg
256 ms
tumblr_nccjz7pJb01snr2dgo1_500.jpg
382 ms
avatar_db722a134cda_30.png
16 ms
avatar_ed690b505924_30.png
24 ms
avatar_022221dcb330_30.png
92 ms
avatar_2451b1eab1db_30.png
17 ms
tumblr_nhe5zbZTd11sry6yko1_500.jpg
17 ms
tumblr_nfy9521VHM1shohxho1_500.jpg
17 ms
tumblr_nbfqqwGWNl1qe130jo1_500.jpg
19 ms
blogger.js
116 ms
athenability.json
241 ms
fishink.us
126 ms
impixu
228 ms
impixu
132 ms
analytics.html
139 ms
TzghnhfCn7TuE73f-CBQ0DmuEnbvkdF7vjbeHX60E38.ttf
120 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
120 ms
login_check.html
13 ms
pyramid_closed_40.png
26 ms
iframe_logo.png
36 ms
rapid-3.36.js
33 ms
rapidworker-1.2.js
27 ms
ga.js
43 ms
analytics.js
69 ms
cs.js
93 ms
__utm.gif
29 ms
cedexis.radar.js
6 ms
fishink.us accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
fishink.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
fishink.us SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fishink.us 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 Fishink.us 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.
fishink.us
Open Graph data is detected on the main page of Fishink. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: