4.9 sec in total
330 ms
3.6 sec
975 ms
Visit tw.epochtimes.com now to see the best up-to-date Tw Epochtimes content for China and also check out these interesting facts you probably never knew about tw.epochtimes.com
台灣
Visit tw.epochtimes.comWe analyzed Tw.epochtimes.com page load time and found that the first response time was 330 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.
tw.epochtimes.com performance score
name
value
score
weighting
Value3.1 s
47/100
10%
Value4.6 s
34/100
25%
Value14.2 s
1/100
10%
Value3,650 ms
1/100
30%
Value0.859
4/100
15%
Value22.5 s
1/100
10%
330 ms
271 ms
260 ms
268 ms
194 ms
Our browser made a total of 146 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Tw.epochtimes.com, 25% (37 requests) were made to I.epochtimes.com and 16% (23 requests) were made to Epochtimes.com. The less responsive or slowest element that took the longest time to load (815 ms) relates to the external source Hi.districtm.ca.
Page size can be reduced by 881.9 kB (47%)
1.9 MB
1.0 MB
In fact, the total size of Tw.epochtimes.com main page is 1.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 762.3 kB which makes up the majority of the site volume.
Potential reduce by 239.4 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. This page needs HTML code to be minified as it can gain 50.1 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 239.4 kB or 84% of the original size.
Potential reduce by 20.5 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. Tw Epochtimes images are well optimized though.
Potential reduce by 448.0 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 448.0 kB or 71% of the original size.
Potential reduce by 174.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. Tw.epochtimes.com needs all CSS files to be minified and compressed as it can save up to 174.1 kB or 86% of the original size.
Number of requests can be reduced by 77 (54%)
142
65
The browser has sent 142 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Tw Epochtimes. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 32 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
tw.epochtimes.com
330 ms
foundation.min.css
271 ms
global.css
260 ms
jquery.bxslider.css
268 ms
plain.css
194 ms
v3.0.102522.js
815 ms
currency.js
814 ms
v4.0.header.min.js
64 ms
jquery.min.js
233 ms
foundation.min.js
318 ms
jquery.laziestloader.min.js
237 ms
bottom.js
318 ms
highlighter.js
385 ms
jcarousellite_1.0.1.min.js
453 ms
jquery.bxslider.min.js
430 ms
plain.js
417 ms
default_category.js
515 ms
i
452 ms
ET_Logo_2_cn.png
449 ms
191778-450x300.jpg
458 ms
191736_medium-450x299.jpg
478 ms
1512200725372330-450x272.jpg
473 ms
20160408PHO0074l-450x327.jpg
458 ms
1602241440082378-450x300.jpg
456 ms
1510140934401770-450x300.jpg
477 ms
16040607533420-450x273.jpg
480 ms
191778-150x120.jpg
477 ms
191736_medium-150x120.jpg
479 ms
1512200725372330-150x120.jpg
480 ms
20160408PHO0074l-150x120.jpg
481 ms
1602241440082378-150x120.jpg
492 ms
1510140934401770-150x120.jpg
493 ms
16040607533420-150x120.jpg
493 ms
160407041135100088-450x300.jpg
494 ms
146012258980-450x238.jpg
497 ms
DSCN2030-450x300.jpg
495 ms
191758-450x300.jpg
500 ms
191767_medium-450x338.jpg
500 ms
191737_medium-450x300.jpg
536 ms
191685_medium-450x297.jpg
496 ms
191716-450x300.jpg
497 ms
191759_medium-450x342.jpg
537 ms
191695-450x300.jpg
537 ms
191735_medium-450x253.jpg
538 ms
191701-450x300.jpg
539 ms
191698-450x189.jpg
539 ms
160407061535100088-450x300.jpg
538 ms
16040708380320-450x300.jpg
540 ms
16040706184420-450x300.jpg
540 ms
16040612255220-450x338.jpg
540 ms
1604080348011758-450x340.jpg
803 ms
1604080357202691-450x307.jpg
791 ms
1604080426522691-450x338.jpg
799 ms
16040612412020-450x300.jpg
801 ms
160407061300100088-450x299.jpg
799 ms
Search-icon.png
435 ms
ET_Logo_2_en.png
438 ms
white.png
432 ms
gtm.js
452 ms
gpt.js
431 ms
header_bg.jpg
87 ms
organge-dot.gif
350 ms
leftbutton.jpg
369 ms
rightbutton.jpg
390 ms
mobile-icon.png
361 ms
16040706184120-450x300.jpg
360 ms
pubads_impl_83.js
433 ms
376 ms
analytics.js
255 ms
quant.js
189 ms
DFPAudiencePixel;ord=2041992282029.2412;dc_seg=68891170
254 ms
atrk.js
528 ms
activityi;src=4979777;type=invmedia;cat=gvjqwgam;ord=3841081298887.7295
532 ms
bx_loader.gif
168 ms
allpages_bottom.htm
295 ms
DFPAudiencePixel;ord=7618991748895.496;dc_seg=68033050
305 ms
DFPAudiencePixel;ord=9475129141937.941;dc_seg=68890690
303 ms
DFPAudiencePixel;ord=2770477037411.183;dc_seg=68889850
311 ms
DFPAudiencePixel;ord=9460529503412.545;dc_seg=68889130
308 ms
DFPAudiencePixel;ord=8199572954326.868;dc_seg=68891290
305 ms
DFPAudiencePixel;ord=8350725788623.095;dc_seg=68889370
309 ms
DFPAudiencePixel;ord=2653602322097.8677;dc_seg=68033170
348 ms
DFPAudiencePixel;ord=8623615514952.689;dc_seg=68889490
347 ms
DFPAudiencePixel;ord=8031929058488.458;dc_seg=70518490
388 ms
DFPAudiencePixel;ord=9300238250289.113;dc_seg=68891530
371 ms
DFPAudiencePixel;ord=8511689701117.575;dc_seg=68820010
370 ms
DFPAudiencePixel;ord=8705648863688.111;dc_seg=68822050
368 ms
DFPAudiencePixel;ord=8718978909309.953;dc_seg=68033290
436 ms
DFPAudiencePixel;ord=1035827894229.4419;dc_seg=73779850
436 ms
DFPAudiencePixel;ord=9086614237166.941;dc_seg=74880610
444 ms
DFPAudiencePixel;ord=4507122072391.212;dc_seg=92048890
442 ms
DFPAudiencePixel;ord=7415663523133.844;dc_seg=92808370
442 ms
DFPAudiencePixel;ord=9003887297585.607;dc_seg=153426730
444 ms
arrow-buttons.png
283 ms
collect
141 ms
pixel;r=1439243563;a=p-a128V7tctPVtT;fpan=1;fpa=P0-678278046-1460129068328;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1460129068327;tzo=-180;ref=;url=http%3A%2F%2Ftw.epochtimes.com%2F;ogl=locale.zh_CN%2Ctype.object%2Ctitle.%E5%8F%B0%E6%B9%BE%E6%96%B0%E9%97%BB%20-%20%E5%A4%A7%E7%BA%AA%E5%85%83%2Cdescription.%E5%8F%B0%E6%B9%BE%E6%96%B0%E9%97%BB%2Curl.http%3A%2F%2Fwww%252Eepochtimes%252Ecom%2Fgb%2Fnsc414%252Ehtm%2Csite_name.%E5%A4%A7%E7%BA%AA%E5%85%83%20www%252Eepochtimes%252Ecom%2Cimage.http%3A%2F%2Fi%252Eepochtimes%252Ecom%2Fassets%2Fuploads%2F2016%2F03%2FDJY_og_image%252Ejpg
251 ms
gshowad.js
205 ms
getjs.static.js
253 ms
container.html
208 ms
collect
380 ms
ads
665 ms
gemini.js
377 ms
close_circle.png
157 ms
ads
327 ms
ads
264 ms
AdCallAggregator
354 ms
AdCallAggregator
197 ms
AdCallAggregator
276 ms
AdCallAggregator
294 ms
AdCallAggregator
299 ms
atrk.gif
233 ms
test.png
354 ms
showad.js
81 ms
PugMaster
82 ms
format.js
122 ms
g-d-min.js
83 ms
ssi
508 ms
osd.js
52 ms
p-P7x87XHnVfbWr.gif
51 ms
9C33F43A-CD55-4682-8A32-8138AC45D3CE
175 ms
pixel
60 ms
demconf.jpg
129 ms
420486.gif
126 ms
Pug
133 ms
teads-format.min.js
196 ms
Pug
111 ms
imgad
304 ms
tags.js
594 ms
imgad
346 ms
Pug
228 ms
track
270 ms
iframe
148 ms
teads-format.css
48 ms
ad
144 ms
ssi
145 ms
sync
188 ms
ssi
161 ms
um
59 ms
generic
56 ms
um
54 ms
ssi
106 ms
um
15 ms
um
18 ms
um
25 ms
um
7 ms
pixel.gif
40 ms
tw.epochtimes.com accessibility score
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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
tw.epochtimes.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
tw.epochtimes.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Tw.epochtimes.com 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 Tw.epochtimes.com 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.
tw.epochtimes.com
Open Graph description is not detected on the main page of Tw Epochtimes. 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: