Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

pridewatch.tw

PrideWatch | 彩虹選民投票指南

Page Load Speed

4.8 sec in total

First Response

251 ms

Resources Loaded

3.9 sec

Page Rendered

631 ms

pridewatch.tw screenshot

About Website

Visit pridewatch.tw now to see the best up-to-date Pride Watch content for Taiwan and also check out these interesting facts you probably never knew about pridewatch.tw

你知道2016年總統、立委、政黨票該投給誰嗎?先來看看他們對同志婚姻的表態再決定吧!提供你最即時完整的政治人物對於同志婚姻的表態數據。

Visit pridewatch.tw

Key Findings

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

Performance Metrics

pridewatch.tw performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value8.0 s

22/100

10%

TBT (Total Blocking Time)

Value170 ms

93/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

pridewatch.tw

251 ms

2428 ms

css_RxyL8FcIMU5l1wUHb18Wvte-CILGNuDxnq83wAmbLlM.css

130 ms

css_8I8tOCPjIVP6mfeMJ_e9IPVH1CnLb6wMloNuja55pnc.css

131 ms

css_GAGeU28hOPt4E1caCFZFRh4qyfThFNjK2SqLL2rzDJs.css

193 ms

Our browser made a total of 55 requests to load all elements on the main page. We found that 95% of them (52 requests) were addressed to the original Pridewatch.tw, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Pridewatch.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 606.8 kB (44%)

Content Size

1.4 MB

After Optimization

787.5 kB

In fact, the total size of Pridewatch.tw main page is 1.4 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 618.9 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 65.8 kB

  • Original 81.7 kB
  • After minification 78.2 kB
  • After compression 15.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. 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 65.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 33.4 kB

  • Original 618.9 kB
  • After minification 585.6 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. Pride Watch images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 264.2 kB

  • Original 401.9 kB
  • After minification 359.1 kB
  • After compression 137.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 264.2 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 243.5 kB

  • Original 291.8 kB
  • After minification 288.5 kB
  • After compression 48.3 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. Pridewatch.tw needs all CSS files to be minified and compressed as it can save up to 243.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (31%)

Requests Now

49

After Optimization

34

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

Accessibility Review

pridewatch.tw accessibility score

62

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.

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

Links do not have a discernible 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

pridewatch.tw best practices score

75

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

SEO Factors

pridewatch.tw SEO score

86

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

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 Pridewatch.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 Pridewatch.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 Pride Watch. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: