4.8 sec in total
103 ms
3.7 sec
1 sec
Click here to check amazing Purple Platypus content. Otherwise, check out these important facts you probably never knew about purpleplatypus.com
Your preferred dealer for Stratasys 3D printers, Onulis 3D printers, eviXscan 3D scanners, ProtoMAX waterjets, Roland DG benchtop milling machines, DyeMansion post processing equipment, and Materialis...
Visit purpleplatypus.comWe analyzed Purpleplatypus.com page load time and found that the first response time was 103 ms and then it took 4.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
purpleplatypus.com performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value13.7 s
0/100
25%
Value11.2 s
5/100
10%
Value1,140 ms
22/100
30%
Value0.1
90/100
15%
Value23.4 s
1/100
10%
103 ms
1828 ms
108 ms
107 ms
103 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 73% of them (77 requests) were addressed to the original Purpleplatypus.com, 10% (11 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Purpleplatypus.com.
Page size can be reduced by 279.6 kB (5%)
5.2 MB
4.9 MB
In fact, the total size of Purpleplatypus.com main page is 5.2 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. 70% of websites need less resources to load. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 178.3 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 178.3 kB or 83% of the original size.
Potential reduce by 90.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. Purple Platypus images are well optimized though.
Potential reduce by 2.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 7.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. Purpleplatypus.com has all CSS files already compressed.
Number of requests can be reduced by 72 (81%)
89
17
The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Purple Platypus. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 32 to 1 for CSS and as a result speed up the page load time.
purpleplatypus.com
103 ms
purpleplatypus.com
1828 ms
mediaelementplayer-legacy.min.css
108 ms
wp-mediaelement.min.css
107 ms
styles.css
103 ms
ml-responsive-table.css
112 ms
dashicons.min.css
125 ms
uploadify.css
108 ms
css
53 ms
style.css
183 ms
style.css
188 ms
elementor-icons.min.css
193 ms
frontend.min.css
207 ms
swiper.min.css
201 ms
post-23388.css
215 ms
frontend.min.css
303 ms
global.css
275 ms
post-29149.css
282 ms
display-structure.css
289 ms
pum-site-styles.css
291 ms
masterslider.main.css
316 ms
custom.css
364 ms
style.css
370 ms
all.css
160 ms
v4-shims.css
200 ms
general.min.css
377 ms
sharing.css
380 ms
social-logos.min.css
390 ms
css
62 ms
fontawesome.min.css
385 ms
solid.min.css
444 ms
jquery.min.js
469 ms
jquery-migrate.min.js
456 ms
nfpluginsettings.js
468 ms
ml.responsive.table.min.js
472 ms
swfobject.js
472 ms
underscore-before.js
756 ms
underscore.min.js
543 ms
underscore-after.js
549 ms
backbone.min.js
552 ms
front-end-deps.js
555 ms
js
71 ms
js
108 ms
qgy67i6dxwvenaxp1rehnwlwqmmea6zo.js
151 ms
e-202405.js
31 ms
animations.min.css
548 ms
front-end.js
540 ms
email-decode.min.js
454 ms
index.js
536 ms
index.js
537 ms
cf7-google-analytics.min.js
530 ms
rmp-menu.js
515 ms
render.c0490812d97b27f61ea7.js
56 ms
jquery.uploadify.v2.1.4.min.js
539 ms
easy-table.css
540 ms
default.js
530 ms
core.min.js
526 ms
pum-site-scripts.js
591 ms
general.min.js
683 ms
imagesloaded.min.js
622 ms
webpack-pro.runtime.min.js
822 ms
webpack.runtime.min.js
609 ms
css
28 ms
frontend-modules.min.js
608 ms
wp-polyfill-inert.min.js
584 ms
regenerator-runtime.min.js
581 ms
wp-polyfill.min.js
602 ms
hooks.min.js
528 ms
i18n.min.js
587 ms
frontend.min.js
583 ms
waypoints.min.js
618 ms
frontend.min.js
617 ms
elements-handlers.min.js
646 ms
logo@2x.png
302 ms
Showroom-Mark-Talena-gray-1-scaled.jpg
378 ms
IMG_0777-scaled.jpg
379 ms
aaaa.png
464 ms
IMG_5173-1-768x512.jpg
420 ms
IMG_5115-768x512.jpg
420 ms
labels-768x360.png
421 ms
IMG_4236-768x512.jpg
483 ms
LOGOS-6.png
512 ms
Untitled-3.png
497 ms
Untitled-3-1.png
501 ms
new.jpg
542 ms
symbol-defs.svg
536 ms
js
99 ms
analytics.js
96 ms
165 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
173 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
200 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
242 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
274 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
273 ms
fa-solid-900.woff
747 ms
fa-solid-900.woff
208 ms
fa-regular-400.woff
208 ms
KFOlCnqEu92Fr1MmWUlfBBc9.ttf
263 ms
KFOlCnqEu92Fr1MmYUtfBBc9.ttf
271 ms
KFOlCnqEu92Fr1MmEU9fBBc9.ttf
272 ms
KFOmCnqEu92Fr1Mu4mxP.ttf
271 ms
KFOlCnqEu92Fr1MmSU5fBBc9.ttf
291 ms
KFOkCnqEu92Fr1MmgVxIIzc.ttf
291 ms
insight.min.js
207 ms
collect
128 ms
127 ms
purpleplatypus.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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
purpleplatypus.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
purpleplatypus.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Purpleplatypus.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Purpleplatypus.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.
purpleplatypus.com
Open Graph data is detected on the main page of Purple Platypus. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: