90.8 sec in total
6.6 sec
83.6 sec
543 ms
Welcome to 3d2013.com homepage info - get ready to check 3 D 2013 best content for China right away, or after learning these important things about 3d2013.com
3D打印在线-无限三维(青岛)电子商务有限公司是典型的互联网+,是3D打印与互联网结合的充分体现
Visit 3d2013.comWe analyzed 3d2013.com page load time and found that the first response time was 6.6 sec and then it took 84.1 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 35 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
3d2013.com performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value3.3 s
70/100
25%
Value6.5 s
39/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value3.3 s
94/100
10%
6620 ms
2800 ms
3068 ms
6678 ms
5860 ms
Our browser made a total of 168 requests to load all elements on the main page. We found that 14% of them (23 requests) were addressed to the original 3d2013.com, 70% (117 requests) were made to Data.3d2013.com and 4% (7 requests) were made to Hb.crm2.qq.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Data.3d2013.com.
Page size can be reduced by 608.4 kB (29%)
2.1 MB
1.5 MB
In fact, the total size of 3d2013.com main page is 2.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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 146.8 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 57.2 kB, which is 34% 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 146.8 kB or 86% of the original size.
Potential reduce by 188.1 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. Obviously, 3 D 2013 needs image optimization as it can save up to 188.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 142.7 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 142.7 kB or 54% of the original size.
Potential reduce by 130.8 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. 3d2013.com needs all CSS files to be minified and compressed as it can save up to 130.8 kB or 82% of the original size.
Number of requests can be reduced by 44 (34%)
128
84
The browser has sent 128 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 3 D 2013. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
3d2013.com
6620 ms
base.css
2800 ms
home_header.css
3068 ms
home_login.css
6678 ms
font-awesome.min.css
5860 ms
jquery.js
7863 ms
common.js
3507 ms
jquery.ui.js
19997 ms
jquery.validation.min.js
2056 ms
jquery.masonry.js
2753 ms
dialog.js
4192 ms
index.css
8405 ms
home_index.js
2737 ms
goodnews.js
3673 ms
index.php
894 ms
index.php
995 ms
chat.css
3190 ms
home_login.css
2881 ms
jquery.charCount.js
1970 ms
jquery.smilies.js
2906 ms
user.js
8141 ms
wpa.php
642 ms
jquery.cookie.js
1833 ms
perfect-scrollbar.min.css
1833 ms
perfect-scrollbar.min.js
5680 ms
jquery.qtip.min.js
9543 ms
jquery.qtip.min.css
3231 ms
compare.js
1190 ms
dialog.css
453 ms
app_bar_bg.png
2317 ms
category-pic-530.jpg
2122 ms
logo.gif
1066 ms
yyzz.jpg
3556 ms
toolbar.png
13762 ms
appbar-hide.png
543 ms
loading.gif
488 ms
certs-big-bg.png
1614 ms
tip_pic4.jpg
490 ms
knet6.jpg
1800 ms
default_user_portrait.gif
874 ms
04862120495511032.jpg
1941 ms
04834700895843595.png
1340 ms
mb_app.png
1755 ms
web-101-102-1-1.jpg
4930 ms
web-101-102-1-2.jpg
9590 ms
web-101-102-1-3.jpg
8245 ms
1_05090208205070085_240.jpg
5641 ms
1_04872532753297345_240.jpg
9967 ms
1_04842492376438303_240.gif
5688 ms
1_04843941319855223_240.jpg
10269 ms
1_04874252141106134_240.jpg
8459 ms
1_04874139539356742_240.jpg
12261 ms
1_04848387584085114_240.jpg
13138 ms
1_04847543423517937_240.jpg
15991 ms
1_05034232916794119_240.jpg
12298 ms
1_05028956061318038_240.jpg
16296 ms
1_04849161706444505_240.jpg
12790 ms
1_04844106843854968_240.png
17405 ms
1_04844244407651809_240.jpg
17040 ms
1_05034916904743446_240.jpg
14929 ms
1_05060964306642553_240.jpg
18377 ms
1_04865712265686654_240.jpg
17572 ms
1_04865698138954132_240.jpg
18724 ms
1_04841384843528012_240.gif
20480 ms
1_04878562091342584_240.jpg
20479 ms
1_04928023611825539_240.jpg
20480 ms
1_04889928470203965_240.jpg
19989 ms
1_04848301463944671_240.jpg
20479 ms
1_04872651316358391_240.png
20480 ms
1_04841398694560993_240.gif
20479 ms
1_04904433042669350_240.jpg
20480 ms
1_04841604080432808_240.jpg
20489 ms
1_04841584508422817_240.jpg
20489 ms
1_04858665406134164_240.jpg
20489 ms
gangting.gif
1356 ms
top_bg.png
823 ms
weixin.png
3617 ms
1_04841407789836914_240.gif
20450 ms
app.gif
1680 ms
home_bg.png
12447 ms
fontawesome-webfont.woff
8743 ms
stat.php
1913 ms
web-2-23.jpg
19645 ms
1_04847606655711961_240.jpg
20157 ms
1_04847631450019102_240.jpg
19742 ms
1_04841381857106648_240.gif
19560 ms
stat.htm
399 ms
core.php
719 ms
9.gif
1137 ms
pic.gif
2335 ms
Panel.js
803 ms
localStorage.js
1093 ms
contains.js
261 ms
app.gif
929 ms
r.cgi
949 ms
ta.php
603 ms
crmqq.php
16177 ms
wpa_first_heart_beat.php
713 ms
1_04847667028692394_240.jpg
17660 ms
1_04847568649726900_240.jpg
19312 ms
1_04849158507431524_240.jpg
19800 ms
1_04865699863414295_240.jpg
20083 ms
1_04826698727453135_240.png
17342 ms
1_04826698353494407_240.png
16983 ms
1_05095533721565231_240.jpg
15343 ms
1_04847648603363052_240.jpg
18584 ms
04841527811363174_sm.jpg
14642 ms
04841532548785650_sm.gif
14575 ms
04841531894619462_sm.gif
14898 ms
04884569979206071_sm.jpg
15243 ms
04844836943424955_sm.jpg
13526 ms
04826065710429551_sm.jpg
11415 ms
04841332656732500_sm.gif
12119 ms
04841515758868268_sm.gif
11144 ms
05031455166787866_sm.jpg
13352 ms
04880264146348269_small.jpg
12211 ms
04841397203309814_sm.jpg
12253 ms
05102318031712780_sm.jpg
10609 ms
web-2-28-1.jpg
20484 ms
web-3-33.jpg
19995 ms
1_04858827615038593_240.jpg
13130 ms
1_04830120150877396_240.jpg
15802 ms
1_04858866581145232_240.png
16320 ms
1_04872468075437919_240.jpg
16172 ms
1_04858898172721413_240.jpg
16195 ms
1_04858915149019734_240.png
19981 ms
1_05034929342559407_240.jpg
19981 ms
1_04834736954577612_240.jpg
17986 ms
04858618931594419_sm.jpg
17693 ms
04858624892641659_sm.jpg
19137 ms
04934822074156779_sm.jpg
19952 ms
04871742151726914_sm.jpg
19994 ms
04843275896039501_sm.jpg
19994 ms
04844249474751264_sm.jpg
19985 ms
04841478969433776_sm.gif
19352 ms
04890016834605884_sm.jpg
16949 ms
04841419878160668_sm.jpg
17662 ms
04841472441313588_sm.jpg
20000 ms
04847657523884150_sm.jpg
18584 ms
04826058805640979_sm.jpg
17396 ms
web-3-38-2.jpg
18026 ms
web-1-13.jpg
19580 ms
1_04834652087274297_240.jpg
19362 ms
hb.crm2.qq.com
626 ms
1_04834641859620473_240.jpg
19793 ms
1_04834647939725521_240.jpg
20296 ms
1_04834649559034008_240.jpg
17975 ms
1_04834650906200292_240.jpg
18893 ms
1_04834653261805118_240.jpg
19605 ms
1_04834664669389010_240.jpg
20025 ms
1_04834698474539311_240.gif
18516 ms
04841488110520867_sm.jpg
18746 ms
04841489263994387_sm.gif
17958 ms
04841488485654038_sm.jpg
17954 ms
04841485937157189_sm.jpg
19723 ms
hb.crm2.qq.com
726 ms
04841489784293203_sm.gif
19863 ms
05053162457290545_sm.jpg
14511 ms
web-1-18-2.jpg
17923 ms
05031592118812418.gif
19793 ms
web-101-101-1.jpg
19671 ms
hb.crm2.qq.com
636 ms
web-101-101-4.jpg
20282 ms
web-101-101-2.jpg
19992 ms
hb.crm2.qq.com
3628 ms
hb.crm2.qq.com
623 ms
hb.crm2.qq.com
1640 ms
hb.crm2.qq.com
610 ms
3d2013.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.
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.
3d2013.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
3d2013.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
ZH
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 3d2013.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that 3d2013.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.
3d2013.com
Open Graph description is not detected on the main page of 3 D 2013. 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: