Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 54

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

houseol.tw

台灣房仲網|愛屋線上 房屋買賣,租屋,售屋,建案刊登,包租代管,房仲總部系統的首選網站

Page Load Speed

21.2 sec in total

First Response

2.6 sec

Resources Loaded

18.1 sec

Page Rendered

555 ms

houseol.tw screenshot

About Website

Welcome to houseol.tw homepage info - get ready to check Houseol best content right away, or after learning these important things about houseol.tw

提供房屋 房屋買賣,租屋,房屋出租,新建案,找房子,房地產,免費自租,免費自售刊登,中古屋刊登廣告,買屋、賣屋、租屋的首選網站。 愛屋團隊專營房仲管理系統,房仲網站設計,包管家app,包租代管系統,房仲總部,代銷網,建案網,租屋網,租房網,新建案,售屋網,saas,資訊委外,不動產物件網站平台,VR,格局圖繪製系統,來電系統,台中網頁設計,SEO搜尋引擎關鍵字優化,最佳化服務廠商。

Visit houseol.tw

Key Findings

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

Performance Metrics

houseol.tw performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value24.6 s

0/100

10%

TBT (Total Blocking Time)

Value2,760 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.112

87/100

15%

TTI (Time to Interactive)

Value31.9 s

0/100

10%

Network Requests Diagram

houseol.tw

2565 ms

streamshow.js

430 ms

houseol.css

457 ms

houseol.css

473 ms

ticker.css

458 ms

Our browser made a total of 416 requests to load all elements on the main page. We found that 90% of them (376 requests) were addressed to the original Houseol.tw, 3% (13 requests) were made to Hq.houseol.com.tw and 2% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Houseol.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 489.0 kB (40%)

Content Size

1.2 MB

After Optimization

743.8 kB

In fact, the total size of Houseol.tw main page is 1.2 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. 45% of websites need less resources to load. Images take 762.8 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 278.8 kB

  • Original 305.7 kB
  • After minification 220.6 kB
  • After compression 26.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 85.1 kB, which is 28% 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 278.8 kB or 91% of the original size.

Image Optimization

-13%

Potential reduce by 97.9 kB

  • Original 762.8 kB
  • After minification 664.9 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. Obviously, Houseol needs image optimization as it can save up to 97.9 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 96.3 kB

  • Original 145.4 kB
  • After minification 135.0 kB
  • After compression 49.1 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 96.3 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 15.9 kB

  • Original 18.8 kB
  • After minification 14.1 kB
  • After compression 3.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. Houseol.tw needs all CSS files to be minified and compressed as it can save up to 15.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 310 (75%)

Requests Now

412

After Optimization

102

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

Accessibility Review

houseol.tw accessibility score

73

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

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

<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

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

Best Practices

houseol.tw best practices score

54

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Uses deprecated APIs

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

houseol.tw SEO score

77

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Houseol.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 Houseol.tw main page’s claimed encoding is big5. 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 data is detected on the main page of Houseol. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: