Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

goez.tw

宜蘭住宿網

Page Load Speed

1.4 sec in total

First Response

669 ms

Resources Loaded

678 ms

Page Rendered

82 ms

About Website

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

提供宜蘭住宿資訊,宜蘭旅遊景點,宜蘭民宿,宜蘭飯店,宜蘭住宿,宜蘭飯店,宜蘭旅遊,宜蘭租車,宜蘭美食,礁溪溫泉,國立傳藝中心,羅東夜市,冬山河親水公園

Visit goez.tw

Key Findings

We analyzed Goez.tw page load time and found that the first response time was 669 ms and then it took 760 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster. This domain responded with an error, which can significantly jeopardize Goez.tw rating and web reputation

Performance Metrics

goez.tw performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.2 s

0/100

25%

SI (Speed Index)

Value18.3 s

0/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.073

96/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

goez.tw

669 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Goez.tw and no external sources were called. The less responsive or slowest element that took the longest time to load (669 ms) belongs to the original domain Goez.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 7 B (9%)

Content Size

78 B

After Optimization

71 B

In fact, the total size of Goez.tw main page is 78 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 78 B which makes up the majority of the site volume.

HTML Optimization

-9%

Potential reduce by 7 B

  • Original 78 B
  • After minification 78 B
  • After compression 71 B

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. This web page is already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

goez.tw accessibility score

69

Accessibility Issues

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-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

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

Buttons do not have an accessible name

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

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.

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

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

goez.tw best practices score

58

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

goez.tw SEO score

87

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Goez.tw 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 Goez.tw main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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