4.6 sec in total
212 ms
3.6 sec
790 ms
Welcome to odaily.co homepage info - get ready to check Odaily best content for Taiwan right away, or after learning these important things about odaily.co
挖話題,找好笑,找經典,找正妹
Visit odaily.coWe analyzed Odaily.co page load time and found that the first response time was 212 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
odaily.co performance score
name
value
score
weighting
Value2.7 s
61/100
10%
Value3.4 s
67/100
25%
Value6.1 s
45/100
10%
Value130 ms
96/100
30%
Value0.052
99/100
15%
Value9.6 s
29/100
10%
212 ms
24 ms
361 ms
188 ms
16 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 75% of them (57 requests) were addressed to the original Odaily.co, 8% (6 requests) were made to Pagead2.googlesyndication.com and 5% (4 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Odaily.co.
Page size can be reduced by 2.8 MB (33%)
8.7 MB
5.8 MB
In fact, the total size of Odaily.co main page is 8.7 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. 60% of websites need less resources to load. Images take 8.1 MB which makes up the majority of the site volume.
Potential reduce by 16.5 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 16.5 kB or 71% of the original size.
Potential reduce by 2.4 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. Obviously, Odaily needs image optimization as it can save up to 2.4 MB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 234.3 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 234.3 kB or 68% of the original size.
Potential reduce by 161.7 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. Odaily.co needs all CSS files to be minified and compressed as it can save up to 161.7 kB or 86% of the original size.
Number of requests can be reduced by 9 (13%)
72
63
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odaily. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
odaily.co
212 ms
css
24 ms
style.css
361 ms
style-headers.css
188 ms
adsbygoogle.js
16 ms
logo.jpg
194 ms
jquery.js
517 ms
scripts.js
308 ms
ca-pub-1588858730081542.js
97 ms
zrt_lookup.html
96 ms
show_ads_impl.js
95 ms
social.png
157 ms
pattern07.png
157 ms
bcrumb-arrow.gif
156 ms
0.jpg
253 ms
0.jpg
325 ms
0.jpg
320 ms
0.jpg
375 ms
0.jpg
379 ms
0.png
625 ms
0.jpg
486 ms
0.jpg
622 ms
0.jpg
501 ms
0.jpg
621 ms
0.jpg
622 ms
0.jpg
720 ms
0.jpg
793 ms
0.jpg
896 ms
0.jpg
1071 ms
0.jpg
788 ms
0.jpg
855 ms
0.jpg
1062 ms
0.jpg
1132 ms
0.jpg
1139 ms
0.jpg
1099 ms
0.jpg
1184 ms
0.png
2994 ms
3w.jpg
1359 ms
0.jpg
1387 ms
0.jpg
1419 ms
0.jpg
1428 ms
0.jpg
1529 ms
0.jpg
1708 ms
0.png
1702 ms
0.jpg
1706 ms
_M5k9_BZTkfaM2dnN0vNGw.woff
37 ms
koFYE26bhT88HgRA8f4vbRsxEYwM7FgeyaSgU71cLG0.woff
37 ms
FZa_MODmDkR9DTu5jHSnSRsxEYwM7FgeyaSgU71cLG0.woff
37 ms
0.jpg
1601 ms
ads
419 ms
osd.js
18 ms
0.jpg
1555 ms
0.jpg
1685 ms
0.jpg
1735 ms
jquery.mousewheel.min.js
9 ms
0.png
1943 ms
0.jpg
1747 ms
0.png
1800 ms
0.jpg
1809 ms
0.jpg
1921 ms
0.jpg
1966 ms
0.png
1978 ms
0.jpg
1855 ms
36838060032344804
22 ms
abg.js
26 ms
m_js_controller.js
38 ms
googlelogo_color_112x36dp.png
17 ms
x_button_blue2.png
17 ms
s
15 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
9 ms
0.jpg
1688 ms
0.jpg
1966 ms
0.jpg
2032 ms
0.jpg
2121 ms
footer.png
1758 ms
activeview
25 ms
odaily.co 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-*] attributes do not match their roles
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
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
odaily.co 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
Browser errors were logged to the console
odaily.co SEO score
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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odaily.co can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Odaily.co 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.
odaily.co
Open Graph description is not detected on the main page of Odaily. 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: