Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yilan.com.tw

《Yilan美食生活玩家》

Page Load Speed

7.8 sec in total

First Response

880 ms

Resources Loaded

6.6 sec

Page Rendered

250 ms

yilan.com.tw screenshot

About Website

Click here to check amazing Yilan content for Taiwan. Otherwise, check out these important facts you probably never knew about yilan.com.tw

《Yilan美食生活玩家》由飲食旅遊生活作家葉怡蘭Yilan所創設的網站。觸角廣及生活享樂各種相關領域,涵蓋深度飲食文章、旅遊采風、廚藝手帖、生活風格、閱讀筆記……等,期望從飲食、旅行、生活入手,體驗、尋覓、探索真實的享樂意義。

Visit yilan.com.tw

Key Findings

We analyzed Yilan.com.tw page load time and found that the first response time was 880 ms and then it took 6.9 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

yilan.com.tw performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

51/100

25%

SI (Speed Index)

Value15.5 s

0/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.8 s

2/100

10%

Network Requests Diagram

yilan.com.tw

880 ms

yilan.com.tw

2349 ms

bootstrap.min.css

438 ms

css

38 ms

essentials.css

1087 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Yilan.com.tw, 18% (17 requests) were made to Static.xx.fbcdn.net and 3% (3 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Yilan.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 687.6 kB (29%)

Content Size

2.4 MB

After Optimization

1.7 MB

In fact, the total size of Yilan.com.tw main page is 2.4 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.8 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 59.0 kB

  • Original 73.0 kB
  • After minification 61.5 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 16% 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 59.0 kB or 81% of the original size.

Image Optimization

-26%

Potential reduce by 460.5 kB

  • Original 1.8 MB
  • After minification 1.3 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. Obviously, Yilan needs image optimization as it can save up to 460.5 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-9%

Potential reduce by 21.6 kB

  • Original 253.5 kB
  • After minification 253.2 kB
  • After compression 231.9 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

-50%

Potential reduce by 146.6 kB

  • Original 291.9 kB
  • After minification 289.7 kB
  • After compression 145.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. Yilan.com.tw needs all CSS files to be minified and compressed as it can save up to 146.6 kB or 50% of the original size.

Requests Breakdown

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

Requests Now

85

After Optimization

41

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

Accessibility Review

yilan.com.tw accessibility score

40

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

Image elements do not have [alt] attributes

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

yilan.com.tw best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

yilan.com.tw SEO score

83

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

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yilan.com.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Yilan.com.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 data is detected on the main page of Yilan. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: