Tools & Wizards About Us
submitdiary.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

submitdiary.com

submitdiary.com

Page Load Speed

3.9 sec in total

First Response

1.6 sec

Resources Loaded

2.1 sec

Page Rendered

171 ms

submitdiary.com screenshot

About Website

Welcome to submitdiary.com homepage info - get ready to check Submitdiary best content right away, or after learning these important things about submitdiary.com

Visit submitdiary.com

Key Findings

We analyzed Submitdiary.com page load time and found that the first response time was 1.6 sec and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

submitdiary.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value1.4 s

100/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value500 ms

58/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.8 s

89/100

10%

Network Requests Diagram

submitdiary.com

1614 ms

style.css

71 ms

wp-embed.min.js

140 ms

wp-emoji-release.min.js

80 ms

header.png

121 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that all of those requests were addressed to Submitdiary.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Submitdiary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.9 kB (68%)

Content Size

76.7 kB

After Optimization

24.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Submitdiary.com main page is 76.7 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. Javascripts take 35.2 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 11.3 kB

  • Original 16.3 kB
  • After minification 15.6 kB
  • After compression 5.1 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 11.3 kB or 69% of the original size.

Image Optimization

-7%

Potential reduce by 620 B

  • Original 8.9 kB
  • After minification 8.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. Submitdiary images are well optimized though.

JavaScript Optimization

-77%

Potential reduce by 27.1 kB

  • Original 35.2 kB
  • After minification 35.2 kB
  • After compression 8.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 27.1 kB or 77% of the original size.

CSS Optimization

-80%

Potential reduce by 12.9 kB

  • Original 16.2 kB
  • After minification 13.5 kB
  • After compression 3.3 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. Submitdiary.com needs all CSS files to be minified and compressed as it can save up to 12.9 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (43%)

Requests Now

14

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

submitdiary.com

submitdiary.com

1614 ms

style.css

style.css

71 ms

wp-embed.min.js

wp-embed.min.js

140 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

80 ms

header.png

header.png

121 ms

search-input.png

search-input.png

137 ms

search-button.png

search-button.png

137 ms

nav-bottom.png

nav-bottom.png

133 ms

nav-top.png

nav-top.png

133 ms

icons.png

icons.png

184 ms

rss.png

rss.png

185 ms

arrow1.gif

arrow1.gif

198 ms

footer.png

footer.png

197 ms

pts55f-webfont.woff

pts55f-webfont.woff

263 ms

pts75f-webfont.woff

pts75f-webfont.woff

137 ms

Accessibility Review

submitdiary.com accessibility score

66

Accessibility Issues

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

Image elements do not have [alt] attributes

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

submitdiary.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

submitdiary.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

Page is blocked from indexing

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Submitdiary.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Japanese. Our system also found out that Submitdiary.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

submitdiary.com

Open Graph description is not detected on the main page of Submitdiary. 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: