Access epochweekly.com. 新紀元周刊｜和您攜手，共同走進新的紀元

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value23.6 s

0/100

25%

SI (Speed Index)

Value11.7 s

4/100

10%

TBT (Total Blocking Time)

Value2,200 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.4 s

4/100

10%

epochweekly.com

296 ms

home.css

214 ms

mouseovertabs.css

160 ms

mouseovertabs.js

168 ms

addthis_widget.js

11 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 29% of them (25 requests) were addressed to the original Epochweekly.com, 23% (20 requests) were made to Static.xx.fbcdn.net and 10% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (598 ms) relates to the external source Images.epochweekly.com.

Content Size

950.3 kB

After Optimization

496.2 kB

In fact, the total size of Epochweekly.com main page is 950.3 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 566.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 54.1 kB

Original 77.0 kB
After minification 74.5 kB
After compression 23.0 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 54.1 kB or 70% of the original size.

Image Optimization

-6%

Potential reduce by 18.8 kB

Original 295.2 kB
After minification 276.4 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. Epochweekly images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 372.4 kB

Original 566.8 kB
After minification 565.1 kB
After compression 194.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 372.4 kB or 66% of the original size.

CSS Optimization

-79%

Potential reduce by 9.0 kB

Original 11.3 kB
After minification 8.8 kB
After compression 2.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. Epochweekly.com needs all CSS files to be minified and compressed as it can save up to 9.0 kB or 79% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

Format your HTML in a way that enables crawlers to better understand your app’s content.

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

JA
Language Claimed

EN
Encoding

BIG5

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Epochweekly.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed English language. Our system also found out that Epochweekly.com 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

epochweekly.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

新紀元周刊｜和您攜手，共同走進新的紀元

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

epochweekly.com

home.css

mouseovertabs.css

mouseovertabs.js

addthis_widget.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

epochweekly.com

home.css

mouseovertabs.css

mouseovertabs.js

addthis_widget.js

LOGO.jpg

image.php

ADBanner_w250.html

ADBanner_w250B.html

image.php

image.php

image.php

image.php

image.php

image.php

image.php

bg_menu.gif

img03.jpg

Search.jpg

imgTxt_001.gif

imgTxt_002.gif

imgTxt_006.gif

imgTxt_004.gif

main_Title.gif

logo_w138.jpg

BG.jpg

submenucontents.htm

ADBanner_w640x040.html

ADBanner_w640.html

BG_RIGHT_BOX_04.gif

gpt.js

all.js

300lo.json

sh.7c7179124ea24ac6ba46caac.html

pubads_impl_81.js

ads

container.html

NewEpoch_Special_TEA-02.jpg

NewEpoch_Special_245.jpg

NewEpoch_onNTDTV.jpg

xd_arbiter.php

xd_arbiter.php

8410671217985061680