Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

event1.rakuya.com.tw

樂屋網|買房、買屋、中古屋、房屋買賣資訊平台,提供完整房價資訊

Page Load Speed

17.4 sec in total

First Response

486 ms

Resources Loaded

16.7 sec

Page Rendered

187 ms

event1.rakuya.com.tw screenshot

About Website

Visit event1.rakuya.com.tw now to see the best up-to-date Event 1 Rakuya content for Taiwan and also check out these interesting facts you probably never knew about event1.rakuya.com.tw

樂屋網為您提供全面的買房、買屋、中古屋及房屋買賣資訊,探索超過30萬筆房屋資料,包括詳盡的中古屋、土地、店面資訊及實價登錄,開始您的房屋探索之旅,透過樂屋網快速找到心中理想的家。

Visit event1.rakuya.com.tw

Key Findings

We analyzed Event1.rakuya.com.tw page load time and found that the first response time was 486 ms and then it took 16.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

event1.rakuya.com.tw performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.7 s

2/100

10%

LCP (Largest Contentful Paint)

Value17.5 s

0/100

25%

SI (Speed Index)

Value15.2 s

1/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

4/100

10%

Network Requests Diagram

event1.rakuya.com.tw

486 ms

www.rakuya.com.tw

2272 ms

main.css

620 ms

1858 ms

menu.css

851 ms

Our browser made a total of 208 requests to load all elements on the main page. We found that 1% of them (3 requests) were addressed to the original Event1.rakuya.com.tw, 19% (40 requests) were made to Rakuya.com.tw and 12% (25 requests) were made to Ads.rakuya.com.tw. The less responsive or slowest element that took the longest time to load (11.2 sec) relates to the external source Static.rakuya.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 891.8 kB (27%)

Content Size

3.3 MB

After Optimization

2.4 MB

In fact, the total size of Event1.rakuya.com.tw main page is 3.3 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 154.0 kB

  • Original 206.2 kB
  • After minification 191.0 kB
  • After compression 52.2 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 154.0 kB or 75% of the original size.

Image Optimization

-4%

Potential reduce by 91.8 kB

  • Original 2.3 MB
  • After minification 2.2 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. Event 1 Rakuya images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 206.9 kB

  • Original 303.7 kB
  • After minification 248.8 kB
  • After compression 96.8 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 206.9 kB or 68% of the original size.

CSS Optimization

-86%

Potential reduce by 439.0 kB

  • Original 507.9 kB
  • After minification 494.6 kB
  • After compression 68.9 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. Event1.rakuya.com.tw needs all CSS files to be minified and compressed as it can save up to 439.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 79 (40%)

Requests Now

199

After Optimization

120

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

Accessibility Review

event1.rakuya.com.tw accessibility score

61

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

button, link, and menuitem elements do not have accessible names.

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.

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

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

event1.rakuya.com.tw best practices score

77

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

High

Page has valid source maps

SEO Factors

event1.rakuya.com.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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Event1.rakuya.com.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 Chinese language. Our system also found out that Event1.rakuya.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 description is not detected on the main page of Event 1 Rakuya. 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: