Tools & Wizards About Us
event.searchome.net screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

event.searchome.net

設計家 Searchome－室內設計、裝潢設計社群平台

Page Load Speed

24.3 sec in total

First Response

442 ms

Resources Loaded

23.7 sec

Page Rendered

209 ms

event.searchome.net screenshot

About Website

Visit event.searchome.net now to see the best up-to-date Event Searchome content for Taiwan and also check out these interesting facts you probably never knew about event.searchome.net

漂亮家居雜誌延伸之網站品牌，近20萬張完整的室內設計裝潢圖片、大量裝修與室內設計資料庫可供搜尋，提供最精準、快速找室內設計師的配對服務，買家具、看廚房衛浴設...

Visit event.searchome.net

Key Findings

We analyzed Event.searchome.net page load time and found that the first response time was 442 ms and then it took 23.9 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

event.searchome.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value26.7 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.023

100/100

15%

TTI (Time to Interactive)

Value21.8 s

1/100

10%

Network Requests Diagram

event_201205

442 ms

561 ms

reset.css

461 ms

style.css

812 ms

ga.js

252 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 42% of them (8 requests) were addressed to the original Event.searchome.net, 11% (2 requests) were made to Google-analytics.com and 11% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (19.6 sec) relates to the external source Piwik.hmgroup.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 30.3 kB (11%)

Content Size

264.1 kB

After Optimization

233.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Event.searchome.net main page is 264.1 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. 15% of websites need less resources to load. Images take 207.0 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 15.6 kB

  • Original 21.4 kB
  • After minification 18.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.4 kB, which is 11% 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 15.6 kB or 73% of the original size.

Image Optimization

-0%

Potential reduce by 919 B

  • Original 207.0 kB
  • After minification 206.1 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. Event Searchome images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 37 B

  • Original 18.8 kB
  • After minification 18.8 kB
  • After compression 18.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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 13.8 kB

  • Original 17.0 kB
  • After minification 15.1 kB
  • After compression 3.1 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. Event.searchome.net needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Event Searchome. According to our analytics all requests are already optimized.

Network Requests Diagram

event_201205

event_201205

442 ms

561 ms

reset.css

reset.css

461 ms

style.css

style.css

812 ms

ga.js

ga.js

252 ms

piwik.js

piwik.js

19559 ms

__utm.gif

__utm.gif

27 ms

collect

collect

104 ms

indexbg.gif

indexbg.gif

425 ms

atrk.js

atrk.js

182 ms

all.js

all.js

281 ms

indexcut.jpg

indexcut.jpg

1745 ms

nav.gif

nav.gif

678 ms

footer.jpg

footer.jpg

1322 ms

atrk.gif

atrk.gif

53 ms

test.png

test.png

174 ms

150 ms

xd_arbiter.php

xd_arbiter.php

155 ms

xd_arbiter.php

xd_arbiter.php

288 ms

Accessibility Review

event.searchome.net accessibility score

83

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

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.

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

Best Practices

event.searchome.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

event.searchome.net SEO score

83

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Event.searchome.net 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 Event.searchome.net 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

event.searchome.net

Open Graph data is detected on the main page of Event Searchome. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: