Report Summary

  • 95

    Performance

    Renders faster than
    93% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

router.tw

首页 - Tomato 番茄 | Tomtao RAF

Page Load Speed

5.3 sec in total

First Response

1.2 sec

Resources Loaded

3.9 sec

Page Rendered

102 ms

router.tw screenshot

About Website

Click here to check amazing Router content. Otherwise, check out these important facts you probably never knew about router.tw

Tomato RAF+ 可以让普通路由器摇身一变,成为拥有不逊色于商用路由器的功能的路由器, Tomato RAF+ 绝对是你遇到的国内功能最强的Tomato 固件,它是一款适合家用和商用的免费第三方路由器系统。

Visit router.tw

Key Findings

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

Performance Metrics

router.tw performance score

95

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.3 s

99/100

10%

Network Requests Diagram

www.router.tw

1240 ms

tomato.css

324 ms

tomato.js

956 ms

hm.js

942 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 75% of them (3 requests) were addressed to the original Router.tw, 25% (1 request) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Router.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 7.5 kB (31%)

Content Size

24.1 kB

After Optimization

16.6 kB

In fact, the total size of Router.tw main page is 24.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. Only 5% of websites need less resources to load. Javascripts take 14.5 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 5.0 kB

  • Original 7.9 kB
  • After minification 7.0 kB
  • After compression 2.9 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 894 B, 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 5.0 kB or 63% of the original size.

JavaScript Optimization

-16%

Potential reduce by 2.3 kB

  • Original 14.5 kB
  • After minification 14.5 kB
  • After compression 12.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 2.3 kB or 16% of the original size.

CSS Optimization

-18%

Potential reduce by 319 B

  • Original 1.8 kB
  • After minification 1.8 kB
  • After compression 1.4 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. Router.tw needs all CSS files to be minified and compressed as it can save up to 319 B or 18% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

3

After Optimization

3

The browser has sent 3 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Router. According to our analytics all requests are already optimized.

Accessibility Review

router.tw accessibility score

84

Accessibility Issues

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

router.tw 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

router.tw SEO score

77

Search Engine Optimization Advices

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