Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

Page Load Speed

3.3 sec in total

First Response

307 ms

Resources Loaded

2.5 sec

Page Rendered

440 ms

eng.tw screenshot

About Website

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

每日單字。

Visit eng.tw

Key Findings

We analyzed Eng.tw page load time and found that the first response time was 307 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

eng.tw performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

41/100

25%

SI (Speed Index)

Value5.1 s

61/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.9 s

54/100

10%

Network Requests Diagram

eng.tw

307 ms

word.eng.tw

1224 ms

3375562265-css_bundle_v2.css

70 ms

authorization.css

129 ms

plusone.js

107 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Eng.tw, 39% (27 requests) were made to Apis.google.com and 13% (9 requests) were made to Blogger.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Word.eng.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 533.6 kB (79%)

Content Size

679.1 kB

After Optimization

145.5 kB

In fact, the total size of Eng.tw main page is 679.1 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. 65% of websites need less resources to load. HTML takes 562.6 kB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 528.6 kB

  • Original 562.6 kB
  • After minification 540.4 kB
  • After compression 34.0 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 528.6 kB or 94% of the original size.

Image Optimization

-0%

Potential reduce by 18 B

  • Original 48.2 kB
  • After minification 48.2 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. Eng images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 5.0 kB

  • Original 60.3 kB
  • After minification 60.2 kB
  • After compression 55.3 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

-0%

Potential reduce by 6 B

  • Original 8.0 kB
  • After minification 8.0 kB
  • After compression 8.0 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. Eng.tw has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (58%)

Requests Now

66

After Optimization

28

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

Accessibility Review

eng.tw accessibility score

80

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

Document doesn't have a <title> element

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

eng.tw best practices score

83

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

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

eng.tw SEO score

72

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

Document doesn't have a <title> element

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

High

Tap targets are not sized appropriately

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 Eng.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 Eng.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 Eng. 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: