Tools & Wizards About Us
yorki.insanejournal.com screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

yorki.insanejournal.com

yorki's Journal

Page Load Speed

533 ms in total

First Response

26 ms

Resources Loaded

410 ms

Page Rendered

97 ms

yorki.insanejournal.com screenshot

About Website

Welcome to yorki.insanejournal.com homepage info - get ready to check Yorki Insane Journal best content for United States right away, or after learning these important things about yorki.insanejournal.com

Visit yorki.insanejournal.com

Key Findings

We analyzed Yorki.insanejournal.com page load time and found that the first response time was 26 ms and then it took 507 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

yorki.insanejournal.com performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.032

100/100

15%

TTI (Time to Interactive)

Value3.0 s

96/100

10%

Network Requests Diagram

yorki.insanejournal.com

26 ms

yorki.insanejournal.com

69 ms

core.js

81 ms

dom.js

80 ms

httpreq.js

79 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 11% of them (2 requests) were addressed to the original Yorki.insanejournal.com, 47% (9 requests) were made to Insanejournal.com and 16% (3 requests) were made to I.imgur.com. The less responsive or slowest element that took the longest time to load (142 ms) relates to the external source Cur.cursors-4u.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 110.3 kB (22%)

Content Size

504.9 kB

After Optimization

394.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Yorki.insanejournal.com main page is 504.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 15% of websites need less resources to load. Images take 415.1 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 10.1 kB

  • Original 13.8 kB
  • After minification 13.7 kB
  • After compression 3.7 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 10.1 kB or 73% of the original size.

Image Optimization

-9%

Potential reduce by 36.9 kB

  • Original 415.1 kB
  • After minification 378.3 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. Yorki Insane Journal images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 57.2 kB

  • Original 68.2 kB
  • After minification 39.2 kB
  • After compression 11.1 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 57.2 kB or 84% of the original size.

CSS Optimization

-79%

Potential reduce by 6.2 kB

  • Original 7.8 kB
  • After minification 4.3 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. Yorki.insanejournal.com needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (29%)

Requests Now

14

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yorki.insanejournal.com

yorki.insanejournal.com

26 ms

yorki.insanejournal.com

yorki.insanejournal.com

69 ms

core.js

core.js

81 ms

dom.js

dom.js

80 ms

httpreq.js

httpreq.js

79 ms

livejournal.js

livejournal.js

74 ms

esn.js

esn.js

75 ms

lj_base.css

lj_base.css

74 ms

esn.css

esn.css

87 ms

bhatoshinecaps.css

bhatoshinecaps.css

47 ms

tumblr_pipvtn3OQB1qdl9k4_540.jpg

tumblr_pipvtn3OQB1qdl9k4_540.jpg

30 ms

2mCgMm4.png

2mCgMm4.png

35 ms

tumblr_inline_p7kqupUVDV1ss04kv_250.gif

tumblr_inline_p7kqupUVDV1ss04kv_250.gif

31 ms

4197515

4197515

41 ms

userinfo.gif

userinfo.gif

21 ms

cur817.cur

cur817.cur

86 ms

iVqGj5q.png

iVqGj5q.png

37 ms

882UAb1.gif

882UAb1.gif

8 ms

cur817.cur

cur817.cur

142 ms

Accessibility Review

yorki.insanejournal.com 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.

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

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

Image elements do not have [alt] attributes

Best Practices

yorki.insanejournal.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

yorki.insanejournal.com SEO score

46

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

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Yorki.insanejournal.com 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 Yorki.insanejournal.com 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

yorki.insanejournal.com

Open Graph description is not detected on the main page of Yorki Insane Journal. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: