Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    86% of websites

  • 85

    SEO

    Google-friendlier than
    62% of websites

diary.tw

My Program – 我的程式, 我的觀點

Page Load Speed

26.7 sec in total

First Response

2.3 sec

Resources Loaded

23 sec

Page Rendered

1.5 sec

diary.tw screenshot

About Website

Welcome to diary.tw homepage info - get ready to check Diary best content for Taiwan right away, or after learning these important things about diary.tw

Visit diary.tw

Key Findings

We analyzed Diary.tw page load time and found that the first response time was 2.3 sec and then it took 24.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

diary.tw performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

tim

2274 ms

style.css

37 ms

SyntaxHighlighter.css

635 ms

plusone.js

280 ms

EAF2.js

684 ms

Our browser made a total of 146 requests to load all elements on the main page. We found that 29% of them (42 requests) were addressed to the original Diary.tw, 9% (13 requests) were made to Apis.google.com and 7% (10 requests) were made to Feedjit.com. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Bloglines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 419.1 kB (38%)

Content Size

1.1 MB

After Optimization

695.2 kB

In fact, the total size of Diary.tw 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. Images take 558.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 107.6 kB

  • Original 134.3 kB
  • After minification 118.9 kB
  • After compression 26.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. This page needs HTML code to be minified as it can gain 15.3 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 107.6 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 39.5 kB

  • Original 558.5 kB
  • After minification 519.0 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. Diary images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 244.1 kB

  • Original 386.3 kB
  • After minification 366.9 kB
  • After compression 142.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 244.1 kB or 63% of the original size.

CSS Optimization

-79%

Potential reduce by 27.9 kB

  • Original 35.2 kB
  • After minification 28.3 kB
  • After compression 7.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. Diary.tw needs all CSS files to be minified and compressed as it can save up to 27.9 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 81 (60%)

Requests Now

135

After Optimization

54

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

Accessibility Review

diary.tw accessibility score

89

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

Image elements do not have [alt] attributes

Best Practices

diary.tw best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

diary.tw SEO score

85

Search Engine Optimization Advices

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

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Diary.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese 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 Diary.tw 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

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