Tools & Wizards About Us
eprice.com.tw screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

eprice.com.tw

ePrice 比價王 - 買手機、找 3C，看我們就對了！

Page Load Speed

7.8 sec in total

First Response

606 ms

Resources Loaded

7.1 sec

Page Rendered

72 ms

eprice.com.tw screenshot

About Website

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

ePrice 比價王 - 買手機、找 3C，看我們就對了！

Visit eprice.com.tw

Key Findings

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

Performance Metrics

eprice.com.tw performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.5 s

0/100

25%

SI (Speed Index)

Value17.6 s

0/100

10%

TBT (Total Blocking Time)

Value2,260 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value18.5 s

3/100

10%

Network Requests Diagram

eprice.com.tw

606 ms

eprice.com.tw

817 ms

www.eprice.com.tw

1326 ms

bootstrap.min.css

266 ms

header.css

467 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 22% of them (18 requests) were addressed to the original Eprice.com.tw, 54% (45 requests) were made to Img.eprice.com.tw and 4% (3 requests) were made to Securepubads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Img.eprice.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 159.3 kB (5%)

Content Size

3.2 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eprice.com.tw main page is 3.2 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. 70% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-14%

Potential reduce by 22 B

  • Original 152 B
  • After minification 152 B
  • After compression 130 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. 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 22 B or 14% of the original size.

Image Optimization

-2%

Potential reduce by 43.4 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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. EPrice images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 114.5 kB

  • Original 768.3 kB
  • After minification 768.2 kB
  • After compression 653.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 114.5 kB or 15% of the original size.

CSS Optimization

-16%

Potential reduce by 1.4 kB

  • Original 8.3 kB
  • After minification 8.3 kB
  • After compression 6.9 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. Eprice.com.tw needs all CSS files to be minified and compressed as it can save up to 1.4 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (34%)

Requests Now

79

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eprice.com.tw

eprice.com.tw

606 ms

eprice.com.tw

eprice.com.tw

817 ms

www.eprice.com.tw

www.eprice.com.tw

1326 ms

bootstrap.min.css

bootstrap.min.css

266 ms

header.css

header.css

467 ms

jquery-ui.1.12.1.min.css

jquery-ui.1.12.1.min.css

666 ms

event.mooncake.css

event.mooncake.css

583 ms

main.css

main.css

651 ms

jquery.201809121401.min.js

jquery.201809121401.min.js

1226 ms

bootstrap.min.js

bootstrap.min.js

626 ms

gpt.js

gpt.js

136 ms

adsbygoogle.js

adsbygoogle.js

141 ms

api.js

api.js

79 ms

common.trigger.js

common.trigger.js

664 ms

header.trigger.js

header.trigger.js

777 ms

ga-event.trigger.js

ga-event.trigger.js

835 ms

blueimp-gallery.min.js

blueimp-gallery.min.js

851 ms

jquery.validate.js

jquery.validate.js

860 ms

main.trigger.js

main.trigger.js

858 ms

vote.trigger.js

vote.trigger.js

973 ms

js

js

84 ms

brand

brand

64 ms

addthis_widget.js

addthis_widget.js

102 ms

brandjs.js

brandjs.js

30 ms

ret.js

ret.js

909 ms

analytics.js

analytics.js

171 ms

beacon.js

beacon.js

170 ms

header.gif

header.gif

1307 ms

big.jpg

big.jpg

1352 ms

list.jpg

list.jpg

1113 ms

list.jpg

list.jpg

1111 ms

list.jpg

list.jpg

1104 ms

list.jpg

list.jpg

1115 ms

large.png

large.png

1873 ms

small.png

small.png

1348 ms

small.png

small.png

1307 ms

small.png

small.png

1352 ms

small.png

small.png

1491 ms

large.png

large.png

1895 ms

small.png

small.png

1508 ms

small.png

small.png

1506 ms

small.png

small.png

1509 ms

small.png

small.png

1681 ms

large.png

large.png

2106 ms

large.png

large.png

1910 ms

list.jpg

list.jpg

1707 ms

list.jpg

list.jpg

1874 ms

list.jpg

list.jpg

1905 ms

list.jpg

list.jpg

2067 ms

1920x495-5ce10d0d0f.jpeg

1920x495-5ce10d0d0f.jpeg

2647 ms

compare_icon.gif

compare_icon.gif

2008 ms

top.gif

top.gif

2022 ms

header.ob.gif

header.ob.gif

1955 ms

fb.jpg

fb.jpg

2105 ms

ajax-loader.large.gif

ajax-loader.large.gif

2132 ms

linkid.js

linkid.js

9 ms

collect

collect

22 ms

collect

collect

52 ms

js

js

56 ms

weekly-ranking-no1.png

weekly-ranking-no1.png

2049 ms

large.png

large.png

2251 ms

large.png

large.png

2057 ms

large.png

large.png

2391 ms

large.png

large.png

2234 ms

large.png

large.png

2250 ms

pubads_impl.js

pubads_impl.js

84 ms

recaptcha__en.js

recaptcha__en.js

138 ms

7682122

7682122

131 ms

ads

ads

483 ms

container.html

container.html

41 ms

client.min.js

client.min.js

375 ms

get-products-of-buysafe.php

get-products-of-buysafe.php

295 ms

large.png

large.png

1469 ms

large.png

large.png

1632 ms

large.png

large.png

1650 ms

large.png

large.png

1459 ms

large.png

large.png

1587 ms

large.png

large.png

1780 ms

large.png

large.png

1629 ms

large.png

large.png

1628 ms

large.png

large.png

1698 ms

large.png

large.png

1742 ms

large.png

large.png

1761 ms

Accessibility Review

eprice.com.tw accessibility score

74

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

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

eprice.com.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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

eprice.com.tw SEO score

92

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eprice.com.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 Eprice.com.tw main page’s claimed encoding is . 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

eprice.com.tw

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