Tools & Wizards About Us
friday.tw screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 36

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

friday.tw

遠傳friDay購物

Page Load Speed

4.1 sec in total

First Response

189 ms

Resources Loaded

3.8 sec

Page Rendered

53 ms

friday.tw screenshot

About Website

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

friDay購物提供遠東百貨、SOGO百貨、愛買量販、品牌outlet及3C、居家、流行等全品類共超過80萬件商品，享折價券現領現折、HAPPY GO點數累兌點，7日猶豫期。(原GoHappy快樂購物網)

Visit friday.tw

Key Findings

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

Performance Metrics

friday.tw performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.433

22/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

friday.tw

189 ms

ec-w.shopping.friday.tw

789 ms

app.js

854 ms

chunk-vendors.css

776 ms

index.css

1359 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Friday.tw, 63% (5 requests) were made to Ec-w.shopping.friday.tw and 13% (1 request) were made to Tracking.shopping.friday.tw. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Ec-w.shopping.friday.tw.

Page Optimization Overview & Recommendations

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

Content Size

6.8 MB

After Optimization

6.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Friday.tw main page is 6.8 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. Only 10% of websites need less resources to load. Images take 5.9 MB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 3.3 kB

  • Original 5.3 kB
  • After minification 5.3 kB
  • After compression 2.1 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 3.3 kB or 61% of the original size.

Image Optimization

-2%

Potential reduce by 99.0 kB

  • Original 5.9 MB
  • After minification 5.8 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. Friday images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 494.8 kB

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

CSS Optimization

-83%

Potential reduce by 125.6 kB

  • Original 150.5 kB
  • After minification 149.4 kB
  • After compression 24.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. Friday.tw needs all CSS files to be minified and compressed as it can save up to 125.6 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (50%)

Requests Now

6

After Optimization

3

  • JavaScript
  • CSS

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

Network Requests Diagram

friday.tw

friday.tw

189 ms

ec-w.shopping.friday.tw

ec-w.shopping.friday.tw

789 ms

app.js

app.js

854 ms

chunk-vendors.css

chunk-vendors.css

776 ms

index.css

index.css

1359 ms

chunk-vendors.js

chunk-vendors.js

1751 ms

index.js

index.js

1369 ms

gtm.js

gtm.js

58 ms

Accessibility Review

friday.tw accessibility score

36

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.

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

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

friday.tw 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

friday.tw SEO score

79

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

High

robots.txt is not valid

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 Friday.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 Friday.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

friday.tw

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: