Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

webnode.tw

免費建立網站 - Webnode

Page Load Speed

2.1 sec in total

First Response

395 ms

Resources Loaded

1.4 sec

Page Rendered

353 ms

webnode.tw screenshot

About Website

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

利用 Webnode 的線上編輯器輕易建造漂亮的網站,我們也提供網域與託管的服務。若您有任何問題,我們本地化的客戶服務人員將很樂意提供您需要的幫助 ?

Visit webnode.tw

Key Findings

We analyzed Webnode.tw page load time and found that the first response time was 395 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

webnode.tw performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.8 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value720 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.291

41/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

www.webnode.tw

395 ms

css

65 ms

webnode.package.1-1-109.css

42 ms

webnode.package.basic.1-1-109.js

47 ms

tw.type1.1.15.js

236 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Webnode.tw, 72% (64 requests) were made to D1rv23qj5kas56.cloudfront.net and 10% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (395 ms) belongs to the original domain Webnode.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 353.5 kB (44%)

Content Size

803.9 kB

After Optimization

450.4 kB

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

HTML Optimization

-74%

Potential reduce by 22.8 kB

  • Original 30.6 kB
  • After minification 30.2 kB
  • After compression 7.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 22.8 kB or 74% of the original size.

Image Optimization

-9%

Potential reduce by 28.7 kB

  • Original 328.3 kB
  • After minification 299.6 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. Webnode images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 223.6 kB

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

CSS Optimization

-80%

Potential reduce by 78.5 kB

  • Original 98.5 kB
  • After minification 98.1 kB
  • After compression 20.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. Webnode.tw needs all CSS files to be minified and compressed as it can save up to 78.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (62%)

Requests Now

77

After Optimization

29

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

Accessibility Review

webnode.tw accessibility score

63

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

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

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

SEO Factors

webnode.tw SEO score

86

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

    JA

  • Language Claimed

    TW

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Webnode.tw can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Twi language. Our system also found out that Webnode.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 Webnode. 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: