5.3 sec in total
425 ms
4.5 sec
418 ms
Welcome to digitimes.com homepage info - get ready to check DIGITIMES best content for Taiwan right away, or after learning these important things about digitimes.com
A platform bridging customers and suppliers
Visit digitimes.comWe analyzed Digitimes.com page load time and found that the first response time was 425 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
digitimes.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value5.5 s
19/100
25%
Value6.4 s
40/100
10%
Value100 ms
98/100
30%
Value0.001
100/100
15%
Value5.9 s
66/100
10%
425 ms
1119 ms
667 ms
724 ms
491 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 59% of them (54 requests) were addressed to the original Digitimes.com, 18% (16 requests) were made to Mms.digitimes.com and 5% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Digitimes.com.
Page size can be reduced by 513.4 kB (53%)
961.5 kB
448.1 kB
In fact, the total size of Digitimes.com main page is 961.5 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. 30% of websites need less resources to load. CSS take 362.0 kB which makes up the majority of the site volume.
Potential reduce by 57.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 57.0 kB or 77% of the original size.
Potential reduce by 23.9 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. DIGITIMES images are well optimized though.
Potential reduce by 125.4 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 125.4 kB or 49% of the original size.
Potential reduce by 307.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. Digitimes.com needs all CSS files to be minified and compressed as it can save up to 307.1 kB or 85% of the original size.
Number of requests can be reduced by 25 (28%)
89
64
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of DIGITIMES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
digitimes.com
425 ms
index.asp
1119 ms
jquery-ui-1.8.1.custom.css
667 ms
global.css
724 ms
0.css
491 ms
jquery-1.4.2.min.js
1256 ms
jquery-ui-1.8.1.custom.min.js
1284 ms
jquery.cookie.js
602 ms
adsbygoogle.js
7 ms
onav.gif
465 ms
Lilin20151125leader.gif
1360 ms
digitimes.gif
205 ms
wr29.png
247 ms
1_r.jpg
253 ms
76_s.jpg
224 ms
417_s.jpg
258 ms
65_s.jpg
243 ms
1_s.jpg
407 ms
363_s.jpg
444 ms
348_s.jpg
484 ms
416_s.jpg
491 ms
412_s.jpg
503 ms
413_s.jpg
514 ms
384_s.jpg
610 ms
361_s.jpg
666 ms
360_s.jpg
723 ms
364_s.jpg
736 ms
261_s.jpg
755 ms
370_s.jpg
771 ms
408_s.jpg
812 ms
366_s.jpg
888 ms
preloader.gif
963 ms
rdim.jpg
980 ms
5817_s.jpg
1005 ms
5809_s.jpg
1027 ms
5812_s.jpg
1709 ms
5816_s.jpg
1107 ms
5815_s.jpg
1202 ms
5813_s.jpg
1224 ms
5814_s.jpg
1255 ms
5811_s.jpg
1283 ms
5810_s.jpg
1328 ms
5808_s.jpg
1443 ms
5807_s.jpg
1469 ms
5805_s.jpg
1506 ms
images.aspx
1548 ms
search.png
441 ms
go.png
461 ms
fb.png
474 ms
twitter.png
496 ms
register.png
526 ms
login.png
652 ms
wbg.png
659 ms
lock.gif
689 ms
gr.gif
710 ms
grb.png
742 ms
vm.gif
788 ms
grs.png
880 ms
phbg.gif
878 ms
UVled20150720button.gif
1112 ms
NB20160226rect.gif
1169 ms
Wearable20150727rect.gif
1235 ms
UHDTVearly20140702rec.gif
1367 ms
images.aspx
1523 ms
ca-pub-9450724093575296.js
97 ms
zrt_lookup.html
62 ms
show_ads_impl.js
62 ms
info.png
878 ms
media.jpg
1141 ms
ga.js
39 ms
__utm.gif
37 ms
ads
155 ms
osd.js
5 ms
chart.aspx
1491 ms
chart.aspx
1503 ms
images.aspx
1528 ms
images.aspx
1574 ms
ui-bg_glass_65_ffffff_1x400.png
1531 ms
ui-bg_glass_75_e6e6e6_1x400.png
1676 ms
m_js_controller.js
26 ms
abg.js
40 ms
favicon
54 ms
googlelogo_color_112x36dp.png
35 ms
nessie_icon_tiamat_white.png
21 ms
s
16 ms
x_button_blue2.png
8 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
3 ms
ui-icons_454545_256x240.png
1513 ms
ui-icons_888888_256x240.png
1526 ms
TSE.png
327 ms
notebook.png
280 ms
digitimes.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
[role]s are not contained by their required parent element
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
digitimes.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
digitimes.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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Digitimes.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Digitimes.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.
digitimes.com
Open Graph description is not detected on the main page of DIGITIMES. 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: