Tools & Wizards About Us
potocki.io screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

potocki.io

Tumblr

Page Load Speed

6.6 sec in total

First Response

329 ms

Resources Loaded

2.3 sec

Page Rendered

4 sec

potocki.io screenshot

About Website

Click here to check amazing Potocki content. Otherwise, check out these important facts you probably never knew about potocki.io

Tumblr. Pure effervescent enrichment. Old internet energy. Home of the Reblogs. All the art you never knew you needed. All the fandoms you could wish for. Enough memes to knock out a moderately-sized ...

Visit potocki.io

Key Findings

We analyzed Potocki.io page load time and found that the first response time was 329 ms and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

potocki.io performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

79/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value1,830 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

potocki.io

329 ms

pre_tumblelog.js

116 ms

index.build.css

128 ms

main.min.css

125 ms

css

131 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Potocki.io, 23% (15 requests) were made to Assets.tumblr.com and 18% (12 requests) were made to 64.media.tumblr.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source 64.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.9 kB (9%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Potocki.io main page is 1.3 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. 70% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 101.0 kB

  • Original 128.6 kB
  • After minification 118.3 kB
  • After compression 27.6 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 101.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 13 B

  • Original 1.1 MB
  • After minification 1.1 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. Potocki images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 4.3 kB

  • Original 62.6 kB
  • After minification 62.5 kB
  • After compression 58.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. This website has mostly compressed JavaScripts.

CSS Optimization

-41%

Potential reduce by 17.6 kB

  • Original 42.7 kB
  • After minification 42.6 kB
  • After compression 25.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. Potocki.io needs all CSS files to be minified and compressed as it can save up to 17.6 kB or 41% of the original size.

Requests Breakdown

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

Requests Now

55

After Optimization

27

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

potocki.io

potocki.io

329 ms

pre_tumblelog.js

pre_tumblelog.js

116 ms

index.build.css

index.build.css

128 ms

main.min.css

main.min.css

125 ms

css

css

131 ms

jquery-1.12.2.min.js

jquery-1.12.2.min.js

96 ms

writecapture.js

writecapture.js

127 ms

embedgist.js

embedgist.js

123 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

122 ms

stylesheet.css

stylesheet.css

123 ms

jquery-2.1.3.min.js

jquery-2.1.3.min.js

163 ms

main.js

main.js

102 ms

index.build.js

index.build.js

192 ms

avatar_c262a8a97eca_96.pnj

avatar_c262a8a97eca_96.pnj

342 ms

widgets.js

widgets.js

604 ms

like_iframe.html

like_iframe.html

284 ms

tumblr_inline_o58q10XSoI1t3d6pa_1280.png

tumblr_inline_o58q10XSoI1t3d6pa_1280.png

927 ms

tumblr_inline_o58q1dUWRy1t3d6pa_1280.png

tumblr_inline_o58q1dUWRy1t3d6pa_1280.png

686 ms

tumblr_inline_o58q1uCsdD1t3d6pa_1280.png

tumblr_inline_o58q1uCsdD1t3d6pa_1280.png

1179 ms

tumblr_inline_o58q2ana8g1t3d6pa_1280.png

tumblr_inline_o58q2ana8g1t3d6pa_1280.png

925 ms

tumblr_inline_o58q2lgRle1t3d6pa_1280.png

tumblr_inline_o58q2lgRle1t3d6pa_1280.png

850 ms

tumblr_inline_o58q30z8mK1t3d6pa_1280.png

tumblr_inline_o58q30z8mK1t3d6pa_1280.png

1326 ms

tumblr_inline_o58q3kBx3A1t3d6pa_400.png

tumblr_inline_o58q3kBx3A1t3d6pa_400.png

925 ms

tumblr_inline_o47joy3QLn1t3d6pa_1280.png

tumblr_inline_o47joy3QLn1t3d6pa_1280.png

1186 ms

tumblr_inline_o47medL5NH1t3d6pa_1280.png

tumblr_inline_o47medL5NH1t3d6pa_1280.png

1108 ms

tumblr_inline_o47k4bgxl51t3d6pa_250.png

tumblr_inline_o47k4bgxl51t3d6pa_250.png

970 ms

tumblr_static_2q477p1a0aecscow00s4c0okc_2048_v2.jpg

tumblr_static_2q477p1a0aecscow00s4c0okc_2048_v2.jpg

925 ms

analytics.js

analytics.js

671 ms

impixu

impixu

724 ms

impixu

impixu

713 ms

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

mem5YaGs126MiZpBA-UN_r8OUuhs.ttf

721 ms

mem5YaGs126MiZpBA-UNirkOUuhs.ttf

mem5YaGs126MiZpBA-UNirkOUuhs.ttf

830 ms

analytics.html

analytics.html

499 ms

g.gif

g.gif

626 ms

ace6642e007ef252facc1b228da46478.js

ace6642e007ef252facc1b228da46478.js

639 ms

like_iframe.html

like_iframe.html

254 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

641 ms

1g0svRuZGFwAB9MiuAAAAA==

1g0svRuZGFwAB9MiuAAAAA==

7 ms

fontello.svg

fontello.svg

238 ms

memnYaGs126MiZpBA-UFUKWyV9hrIqY.ttf

memnYaGs126MiZpBA-UFUKWyV9hrIqY.ttf

650 ms

memnYaGs126MiZpBA-UFUKXGUdhrIqY.ttf

memnYaGs126MiZpBA-UFUKXGUdhrIqY.ttf

649 ms

Caslon-Bold-webfont.woff

Caslon-Bold-webfont.woff

308 ms

Caslon-Book-webfont.woff

Caslon-Book-webfont.woff

316 ms

login_check.html

login_check.html

47 ms

avatar_c262a8a97eca_64.pnj

avatar_c262a8a97eca_64.pnj

514 ms

g.gif

g.gif

393 ms

g.gif

g.gif

418 ms

consent

consent

465 ms

cs.js

cs.js

327 ms

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

widget_iframe.96fd96193cc66c3e11d4c5e4c7c7ec97.html

70 ms

collect

collect

179 ms

settings

settings

437 ms

button.63c51c903061d0dbd843c41e8a00aa5a.js

button.63c51c903061d0dbd843c41e8a00aa5a.js

140 ms

gist-embed-00e78e58c090554178aab653e8643d5e.css

gist-embed-00e78e58c090554178aab653e8643d5e.css

286 ms

0627f642064e91af09e2.js

0627f642064e91af09e2.js

207 ms

header.build.js

header.build.js

44 ms

exceptions.js

exceptions.js

45 ms

index.build.js

index.build.js

49 ms

follow_button.96fd96193cc66c3e11d4c5e4c7c7ec97.en.html

follow_button.96fd96193cc66c3e11d4c5e4c7c7ec97.en.html

96 ms

tweet_button.96fd96193cc66c3e11d4c5e4c7c7ec97.en.html

tweet_button.96fd96193cc66c3e11d4c5e4c7c7ec97.en.html

158 ms

cdn.json

cdn.json

207 ms

g.gif

g.gif

139 ms

9bb6ca3b3fd6a84b2153.js

9bb6ca3b3fd6a84b2153.js

145 ms

569b6d6fc42d335c267cfcc4a2912237.js

569b6d6fc42d335c267cfcc4a2912237.js

111 ms

e0f307b4238e0b70ed7d0a775dc7ea28.js

e0f307b4238e0b70ed7d0a775dc7ea28.js

94 ms

jot.html

jot.html

2 ms

Accessibility Review

potocki.io accessibility score

57

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

potocki.io 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

potocki.io SEO score

92

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

    EN

  • Encoding

    UTF-8

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

potocki.io

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