Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 82% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

tsunamiworks.com

愛食記 - 台灣美食餐廳推薦,最好用的美食App

Page Load Speed

4.2 sec in total

First Response

666 ms

Resources Loaded

2.9 sec

Page Rendered

597 ms

tsunamiworks.com screenshot

About Website

Visit tsunamiworks.com now to see the best up-to-date Tsunamiworks content for Taiwan and also check out these interesting facts you probably never knew about tsunamiworks.com

愛食記幫你發現最新、最流行的美食餐廳!! 透過網站和App讓你快速探索全台美食,觀看網友的餐廳評價、部落客專業食記,並提供餐廳24小時線上訂位服務

Visit tsunamiworks.com

Key Findings

We analyzed Tsunamiworks.com page load time and found that the first response time was 666 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

tsunamiworks.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

24/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value1,290 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

tsunamiworks.com

666 ms

bootstrap.min.css

14 ms

bootstrap-switch.min.css

12 ms

font-awesome.min.css

19 ms

main.css

532 ms

Our browser made a total of 114 requests to load all elements on the main page. We found that 3% of them (3 requests) were addressed to the original Tsunamiworks.com, 33% (38 requests) were made to Maps.googleapis.com and 18% (20 requests) were made to Lh3.googleusercontent.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Ifoodie.tw.

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

3.0 MB

In fact, the total size of Tsunamiworks.com main page is 3.8 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 2.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 170.9 kB

  • Original 217.7 kB
  • After minification 205.4 kB
  • After compression 46.8 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 170.9 kB or 79% of the original size.

Image Optimization

-2%

Potential reduce by 48.9 kB

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

JavaScript Optimization

-68%

Potential reduce by 496.2 kB

  • Original 725.3 kB
  • After minification 704.3 kB
  • After compression 229.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 496.2 kB or 68% of the original size.

CSS Optimization

-81%

Potential reduce by 122.3 kB

  • Original 150.5 kB
  • After minification 149.4 kB
  • After compression 28.2 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. Tsunamiworks.com needs all CSS files to be minified and compressed as it can save up to 122.3 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (42%)

Requests Now

106

After Optimization

62

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

Accessibility Review

tsunamiworks.com accessibility score

93

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

Links do not have a discernible name

Best Practices

tsunamiworks.com best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

tsunamiworks.com 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

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 Tsunamiworks.com 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 Tsunamiworks.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

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