Tools & Wizards About Us
idv.st screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

Page Load Speed

2.8 sec in total

First Response

309 ms

Resources Loaded

1.4 sec

Page Rendered

1 sec

idv.st screenshot

About Website

Click here to check amazing Idv content for Taiwan. Otherwise, check out these important facts you probably never knew about idv.st

Visit idv.st

Key Findings

We analyzed Idv.st page load time and found that the first response time was 309 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

idv.st performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.027

100/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

idv.st

309 ms

www.idv.st

259 ms

logo88x31.gif

711 ms

logo1.gif

407 ms

bkgn1.gif

408 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 93% of them (41 requests) were addressed to the original Idv.st, 2% (1 request) were made to My24h.net and 2% (1 request) were made to Centurys.com.tw. The less responsive or slowest element that took the longest time to load (888 ms) relates to the external source Centurys.myweb.hinet.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 323 B (50%)

Content Size

645 B

After Optimization

322 B

  • HTML

In fact, the total size of Idv.st main page is 645 B. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. Only 10% of websites need less resources to load. HTML takes 645 B which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 323 B

  • Original 645 B
  • After minification 576 B
  • After compression 322 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. This page needs HTML code to be minified as it can gain 69 B, 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 323 B or 50% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (47%)

Requests Now

43

After Optimization

23

  • AJAX
  • Images

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

Network Requests Diagram

idv.st

idv.st

309 ms

www.idv.st

www.idv.st

259 ms

logo88x31.gif

logo88x31.gif

711 ms

logo1.gif

logo1.gif

407 ms

bkgn1.gif

bkgn1.gif

408 ms

alliances.gif

alliances.gif

451 ms

bkgn2.gif

bkgn2.gif

421 ms

bkgn3.gif

bkgn3.gif

426 ms

bkgn7.gif

bkgn7.gif

415 ms

bkgn5.gif

bkgn5.gif

418 ms

bkgn6.gif

bkgn6.gif

420 ms

bkgntop.gif

bkgntop.gif

421 ms

bkgnleft.gif

bkgnleft.gif

421 ms

menu11.gif

menu11.gif

420 ms

bkgnright.gif

bkgnright.gif

434 ms

bkgndown.gif

bkgndown.gif

436 ms

menu12.gif

menu12.gif

446 ms

rad.gif

rad.gif

446 ms

logoidv.gif

logoidv.gif

456 ms

banner_uuu_120x60.gif

banner_uuu_120x60.gif

629 ms

logo_my24h_120x60.gif

logo_my24h_120x60.gif

888 ms

c-left.gif

c-left.gif

417 ms

c-center.gif

c-center.gif

413 ms

register.gif

register.gif

413 ms

c-right.gif

c-right.gif

414 ms

start9.gif

start9.gif

412 ms

free.gif

free.gif

411 ms

memberbasic.gif

memberbasic.gif

424 ms

member1.gif

member1.gif

424 ms

member2.gif

member2.gif

423 ms

menu16.gif

menu16.gif

422 ms

code.asp

code.asp

441 ms

logo_0923_120x60.gif

logo_0923_120x60.gif

440 ms

menu17.gif

menu17.gif

440 ms

email.gif

email.gif

437 ms

c-left.gif

c-left.gif

437 ms

c-center.gif

c-center.gif

471 ms

idvst.gif

idvst.gif

472 ms

c-right.gif

c-right.gif

473 ms

start9.gif

start9.gif

464 ms

visitor.gif

visitor.gif

147 ms

counters.gif

counters.gif

168 ms

bkgn4.gif

bkgn4.gif

156 ms

bkgn8.gif

bkgn8.gif

154 ms

Accessibility Review

idv.st accessibility score

33

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

<frame> or <iframe> elements do not have a title

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

idv.st best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

idv.st SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idv.st can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Idv.st 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

idv.st

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