11.2 sec in total
1.2 sec
9.6 sec
417 ms
Welcome to smxdiy.com homepage info - get ready to check SMXDIY best content for China right away, or after learning these important things about smxdiy.com
SMXDIY 玩家技术交流俱乐部 S-MXDIY,国内较好的装机技术论坛,专业改造,魔改,CPU,显卡,主板,硬件,电脑,编程器,修改BIOS,刷机,备份,驱动,内存超频,系统更新,
Visit smxdiy.comWe analyzed Smxdiy.com page load time and found that the first response time was 1.2 sec and then it took 10 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
smxdiy.com performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value3.9 s
53/100
25%
Value6.3 s
42/100
10%
Value20 ms
100/100
30%
Value0
100/100
15%
Value4.0 s
87/100
10%
1240 ms
958 ms
654 ms
2424 ms
663 ms
Our browser made a total of 117 requests to load all elements on the main page. We found that 40% of them (47 requests) were addressed to the original Smxdiy.com, 26% (31 requests) were made to Uploadoss.smxdiy.com and 8% (9 requests) were made to Statics2.smxdiy.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Img1.360buyimg.com.
Page size can be reduced by 273.4 kB (20%)
1.3 MB
1.1 MB
In fact, the total size of Smxdiy.com main page is 1.3 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. Javascripts take 557.7 kB which makes up the majority of the site volume.
Potential reduce by 197.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. This page needs HTML code to be minified as it can gain 35.0 kB, which is 14% 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 197.5 kB or 80% of the original size.
Potential reduce by 52.7 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. SMXDIY images are well optimized though.
Potential reduce by 22.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. This website has mostly compressed JavaScripts.
Potential reduce by 189 B
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. Smxdiy.com has all CSS files already compressed.
Number of requests can be reduced by 30 (31%)
96
66
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SMXDIY. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and as a result speed up the page load time.
www.smxdiy.com
1240 ms
style_5_common.css
958 ms
style_5_forum_index.css
654 ms
common.js
2424 ms
forum.js
663 ms
font-awesome.min.css
904 ms
jquery.min.js
738 ms
jquery.yide.slide.js
733 ms
logging.js
1442 ms
index.js
619 ms
auto.js
880 ms
auto.js
842 ms
logo.png
414 ms
y_icons3.png
236 ms
45fa9ca7c69e2bfca8d93120694c101a.jpg
716 ms
716162fd9a3197c8850b8975f7a8bc0c.jpg
744 ms
d1b18416cc8506b046eb0c1258d83984.jpg
2399 ms
9cc009781dee9ba8c7ee434d2221df2c.jpg
781 ms
bbed23c8c3644130f5d7b148cb6a0707.jpg
806 ms
61172b2e5899422bbc9b632945566c9f.jpg
969 ms
23dbdf8963675e086518e6ba7df28b79.jpg
3169 ms
bd370b326538c79fcde33794a71eae43.jpg
1002 ms
cd0a6e37d03b1a8e916a7a102f552305.jpg
1105 ms
914dfff1498c9039530008841f365079.jpg
1064 ms
d8b658443710464c3435fd80af734f04.jpg
1373 ms
e9f7766f60a5aefa2b25860b37309225.jpg
1245 ms
555c86908aef484029198ef68f8e2fea.jpg
1379 ms
77533a4cd8bfc5fd2f646cbdb6204ff2.jpg
2390 ms
gabaico.gif
2393 ms
qq_login.gif
225 ms
29_avatar_middle.jpg
429 ms
02_avatar_middle.jpg
434 ms
96_avatar_middle.jpg
750 ms
63_avatar_middle.jpg
447 ms
25_avatar_middle.jpg
494 ms
25_avatar_middle.jpg
457 ms
55_avatar_middle.jpg
648 ms
88_avatar_middle.jpg
681 ms
98_avatar_middle.jpg
693 ms
18_avatar_middle.jpg
706 ms
55_avatar_middle.jpg
725 ms
86_avatar_middle.jpg
902 ms
60_avatar_middle.jpg
928 ms
06_avatar_middle.jpg
971 ms
19_avatar_middle.jpg
947 ms
62_avatar_middle.jpg
991 ms
64_avatar_middle.jpg
974 ms
63_avatar_middle.jpg
1100 ms
67_avatar_middle.jpg
1135 ms
06_avatar_middle.jpg
1178 ms
94_avatar_middle.jpg
1371 ms
57_avatar_middle.jpg
1197 ms
56_avatar_middle.jpg
1230 ms
01_avatar_middle.jpg
1374 ms
95_avatar_middle.jpg
1375 ms
collapsed_no.gif
2384 ms
forum_new.gif
2385 ms
forum.gif
2386 ms
collapsed_yes.gif
2387 ms
35_avatar_middle.jpg
2387 ms
40_avatar_middle.jpg
2388 ms
ft_codepic1.png
2391 ms
fontawesome-webfont.woff
803 ms
190127gr2wed4k28ewl20t.png
2347 ms
arrows.gif
2325 ms
auto
413 ms
index.js
108 ms
greenseer.js
85 ms
politicaregular.ttf
2192 ms
category_lbg.png
2165 ms
a
545 ms
tb.png
1987 ms
dot.gif
1993 ms
noavatar_small.gif
1942 ms
vline.png
1968 ms
noavatar_small.gif
1934 ms
top1.png
1967 ms
top2.png
2673 ms
auto
755 ms
noavatar_small.gif
1746 ms
top3.png
2486 ms
yide_gg_icon.png
2484 ms
yide_ft_telicon.png
2474 ms
noavatar_small.gif
1671 ms
5a0e17545ce643039cacedf3175536f1.jpg
1495 ms
66593a848e4b4151ae8e8e7faec2ec95.png
1515 ms
noavatar_small.gif
1450 ms
noavatar_small.gif
1441 ms
noavatar_small.gif
1423 ms
c1
221 ms
noavatar_small.gif
1314 ms
noavatar_small.gif
1292 ms
noavatar_small.gif
1987 ms
noavatar_small.gif
1970 ms
noavatar_small.gif
1935 ms
55efcd1aN19509f1f.png
3404 ms
aea226a9be6fddee.jpg
1787 ms
jdwebm.js
1795 ms
pc-tk.js
1083 ms
handler.js
1082 ms
js_security_v3_0.1.4.js
1737 ms
sha256.js
1792 ms
sign.js
1793 ms
requestApi.js
1793 ms
noavatar_small.gif
1791 ms
noavatar_small.gif
1792 ms
noavatar_small.gif
1248 ms
push.js
2141 ms
noavatar_small.gif
1230 ms
11.0.1.js
1227 ms
jsTk.do
1600 ms
js-security-v3-rac.js
36 ms
c1
471 ms
gatherInfo.js
214 ms
ab77b6ea7f3fbf79.js
454 ms
rac
1406 ms
scrolltop.png
224 ms
smxdiy.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
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
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.
smxdiy.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
smxdiy.com 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
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Smxdiy.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 Smxdiy.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.
smxdiy.com
Open Graph description is not detected on the main page of SMXDIY. 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: