Tools & Wizards About Us
prince.tw screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

prince.tw

新屋網-新成屋-買屋-預售屋網站│New house network

Page Load Speed

4.1 sec in total

First Response

558 ms

Resources Loaded

3.5 sec

Page Rendered

71 ms

prince.tw screenshot

About Website

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

台南新屋提供買屋、新建案、預售屋等台南新屋區資料，新建案資訊最齊全，查詢新建案諮詢專線價格地址等，最新資訊全部一指搞定。找新屋,新建案新成屋請上台南新屋網！

Visit prince.tw

Key Findings

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

Performance Metrics

prince.tw performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value15.4 s

0/100

10%

TBT (Total Blocking Time)

Value1,280 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

prince.tw

558 ms

prince.tw

982 ms

css

35 ms

bootstrap.css

772 ms

style2_0122.css

1463 ms

Our browser made a total of 24 requests to load all elements on the main page. We found that 58% of them (14 requests) were addressed to the original Prince.tw, 17% (4 requests) were made to Googletagmanager.com and 13% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Prince.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (76%)

Content Size

2.1 MB

After Optimization

504.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prince.tw main page is 2.1 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. 40% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 25.2 kB

  • Original 29.6 kB
  • After minification 25.5 kB
  • After compression 4.4 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 4.1 kB, which is 14% 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 25.2 kB or 85% of the original size.

Image Optimization

-9%

Potential reduce by 7.1 kB

  • Original 78.5 kB
  • After minification 71.4 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. Prince images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 872.8 kB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 330.7 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 872.8 kB or 73% of the original size.

CSS Optimization

-87%

Potential reduce by 667.6 kB

  • Original 766.0 kB
  • After minification 615.0 kB
  • After compression 98.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. Prince.tw needs all CSS files to be minified and compressed as it can save up to 667.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (60%)

Requests Now

20

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prince.tw

prince.tw

558 ms

prince.tw

prince.tw

982 ms

css

css

35 ms

bootstrap.css

bootstrap.css

772 ms

style2_0122.css

style2_0122.css

1463 ms

fonts.css

fonts.css

1281 ms

home_0122.css

home_0122.css

559 ms

ckform_home2.js

ckform_home2.js

562 ms

core.min.js

core.min.js

1659 ms

script.js

script.js

930 ms

gtm.js

gtm.js

62 ms

fbevents.js

fbevents.js

30 ms

home_logo.png

home_logo.png

232 ms

ring_bg.svg

ring_bg.svg

231 ms

home_logo1110620.png

home_logo1110620.png

554 ms

materialdesignicons-webfont.woff

materialdesignicons-webfont.woff

449 ms

Linearicons.ttf

Linearicons.ttf

555 ms

js

js

49 ms

analytics.js

analytics.js

25 ms

destination

destination

132 ms

collect

collect

93 ms

collect

collect

89 ms

collect

collect

92 ms

js

js

67 ms

Accessibility Review

prince.tw accessibility score

86

Accessibility Issues

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

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

prince.tw best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

prince.tw SEO score

100

Search Engine Optimization Advices

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 Prince.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 Prince.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

prince.tw

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