Tools & Wizards About Us

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

vedr.tw

VEDR - 行車記錄器互助網::首頁

Page Load Speed

8 sec in total

First Response

1.4 sec

Resources Loaded

6.5 sec

Page Rendered

194 ms

About Website

Click here to check amazing VEDR content for Taiwan. Otherwise, check out these important facts you probably never knew about vedr.tw

VEDR - 行車記錄器互助網::行車記錄器已慢慢形成交通工具的基本配備，不論行車糾紛、車禍、擦撞、碰撞等的事故發生，可以提供簡易交通裁決或重大事件判決的依據，以釐清事件責任歸屬。本站希望藉由影片擁有者透過 上傳影像檔後，利用本站標記影片相關時間、地點等的詳細資料，提供者無償讓所需要的人使用，達到互助讓世界更加美好！(Car crash,Car Accident)

Visit vedr.tw

Key Findings

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

Performance Metrics

vedr.tw performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value23.2 s

1/100

10%

Network Requests Diagram

vedr.tw

1356 ms

style.css

212 ms

jquery.ui.all.css

406 ms

impvar.js

581 ms

jquery-1.7.2.min.js

960 ms

Our browser made a total of 117 requests to load all elements on the main page. We found that 54% of them (63 requests) were addressed to the original Vedr.tw, 19% (22 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Vedr.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.4 kB (19%)

Content Size

584.8 kB

After Optimization

476.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vedr.tw main page is 584.8 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. 70% of websites need less resources to load. Javascripts take 332.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 76.6 kB

  • Original 95.2 kB
  • After minification 86.3 kB
  • After compression 18.7 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 76.6 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 1.7 kB

  • Original 146.9 kB
  • After minification 145.2 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. VEDR images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 26.8 kB

  • Original 332.2 kB
  • After minification 332.2 kB
  • After compression 305.5 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

-32%

Potential reduce by 3.3 kB

  • Original 10.4 kB
  • After minification 10.4 kB
  • After compression 7.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. Vedr.tw needs all CSS files to be minified and compressed as it can save up to 3.3 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 72 (63%)

Requests Now

114

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

vedr.tw accessibility score

75

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

Form elements do not have associated labels

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

List items (<li>) are not contained within <ul> or <ol> parent elements.

High

Cells in a <table> element that use the [headers] attribute refer to an element id not found within the same table.

Best Practices

vedr.tw best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vedr.tw SEO score

69

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

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vedr.tw can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Vedr.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 data is detected on the main page of VEDR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: