9.3 sec in total
882 ms
8 sec
364 ms
Welcome to trulydiy.com homepage info - get ready to check Trulydiy best content right away, or after learning these important things about trulydiy.com
DIY大全, DIY网址大全,各地DIY小店,DIY教程,DIY书籍,DIY作品欣赏
Visit trulydiy.comWe analyzed Trulydiy.com page load time and found that the first response time was 882 ms and then it took 8.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
trulydiy.com performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value3.2 s
73/100
25%
Value4.6 s
71/100
10%
Value350 ms
73/100
30%
Value0
100/100
15%
Value6.8 s
55/100
10%
882 ms
767 ms
674 ms
445 ms
448 ms
Our browser made a total of 85 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Trulydiy.com, 80% (68 requests) were made to 4crafter.com and 6% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (5.2 sec) relates to the external source 4crafter.com.
Page size can be reduced by 354.3 kB (34%)
1.1 MB
698.7 kB
In fact, the total size of Trulydiy.com main page is 1.1 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. 50% of websites need less resources to load. Images take 620.3 kB which makes up the majority of the site volume.
Potential reduce by 100.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 100.0 kB or 86% of the original size.
Potential reduce by 32.6 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. Trulydiy images are well optimized though.
Potential reduce by 146.9 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 146.9 kB or 66% of the original size.
Potential reduce by 74.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. Trulydiy.com needs all CSS files to be minified and compressed as it can save up to 74.7 kB or 78% of the original size.
Number of requests can be reduced by 36 (43%)
83
47
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Trulydiy. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
trulydiy.com
882 ms
www.4crafter.com
767 ms
style_7_common.css
674 ms
style_7_forum_index.css
445 ms
lang_js.js
448 ms
common.js
671 ms
style_7_widthauto.css
446 ms
forum.js
450 ms
logging.js
892 ms
md5.js
899 ms
sharewx.js
900 ms
nge.css
912 ms
api.php
1131 ms
common.js
1120 ms
api.php
1351 ms
yl5361_bg.jpg
915 ms
yl5361_top.png
650 ms
home.gif
872 ms
fav.gif
890 ms
switch_blind.png
1112 ms
en.gif
1112 ms
ar.gif
1127 ms
de.gif
1320 ms
es.gif
1329 ms
fr.gif
1366 ms
kr.gif
1539 ms
pl.gif
1542 ms
ru.gif
1558 ms
zh.gif
1767 ms
tw.gif
1775 ms
th.gif
1803 ms
tr.gif
1981 ms
vn.gif
1991 ms
logo.png
2008 ms
glogin.gif
2216 ms
fblogin.gif
2215 ms
yhlogin.gif
2249 ms
130329uo7ezg124sokuk1d.jpg
2875 ms
103708gutvaau1aicwkbbz.jpg
5230 ms
113725v4e2zg8w8l8nv6e7.jpg
2903 ms
095606tm74yio9y6oc7rt1.jpg
4023 ms
082024jb0hvqxxzl30zq3h.jpg
3123 ms
list10.gif
2679 ms
0.gif
2937 ms
44_avatar_small.jpg
3115 ms
1.gif
3149 ms
04_avatar_small.jpg
3345 ms
common_extra.js
3171 ms
2.gif
3331 ms
61_avatar_small.jpg
3159 ms
adsbygoogle.js
13 ms
analytics.js
11 ms
collapsed_no.gif
3357 ms
push.js
570 ms
forum.gif
3372 ms
ca-pub-3253491736025534.js
69 ms
zrt_lookup.html
64 ms
show_ads_impl.js
75 ms
collect
24 ms
ads
246 ms
osd.js
7 ms
px.png
3358 ms
newarow.gif
3360 ms
pn.png
3785 ms
1149227080962270366
49 ms
abg.js
57 ms
m_js_controller.js
77 ms
googlelogo_color_112x36dp.png
109 ms
nv.png
3594 ms
qmenu.png
3368 ms
nv_a.png
3548 ms
x_button_blue2.png
56 ms
s
66 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
4 ms
search.png
3382 ms
yl5361_pt_bg.jpg
3610 ms
pt_item.png
3751 ms
chart.png
3600 ms
listbg.gif
3599 ms
yl5361_fl_bm_r.gif
3809 ms
yl5361_fl_bm_l.gif
3608 ms
yl5361_fl_bm_c.gif
3783 ms
yl5361_bm_bg.jpg
3788 ms
yl5361_ft_bg.jpg
3613 ms
scrolltop.png
3691 ms
trulydiy.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-*] attributes do not match their roles
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
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>).
trulydiy.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Browser errors were logged to the console
trulydiy.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
ZH
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trulydiy.com 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 Trulydiy.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.
trulydiy.com
Open Graph description is not detected on the main page of Trulydiy. 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: