5.1 sec in total
389 ms
3.5 sec
1.2 sec
Click here to check amazing Createx content for Germany. Otherwise, check out these important facts you probably never knew about createx.de
Visit createx.deWe analyzed Createx.de page load time and found that the first response time was 389 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.
createx.de performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value16.9 s
0/100
25%
Value18.9 s
0/100
10%
Value540 ms
54/100
30%
Value1.333
0/100
15%
Value26.2 s
0/100
10%
389 ms
266 ms
45 ms
122 ms
364 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 83% of them (55 requests) were addressed to the original Createx.de, 14% (9 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Createx.de.
Page size can be reduced by 1.4 MB (22%)
6.3 MB
4.9 MB
In fact, the total size of Createx.de main page is 6.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.6 MB which makes up the majority of the site volume.
Potential reduce by 38.9 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 7.3 kB, which is 16% 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 38.9 kB or 84% of the original size.
Potential reduce by 49.3 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. Createx images are well optimized though.
Potential reduce by 509.5 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 509.5 kB or 70% of the original size.
Potential reduce by 767.6 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. Createx.de needs all CSS files to be minified and compressed as it can save up to 767.6 kB or 86% of the original size.
Number of requests can be reduced by 21 (41%)
51
30
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Createx. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
createx.de
389 ms
266 ms
css
45 ms
bootstrap.min.css
122 ms
essentials.css
364 ms
layout.css
443 ms
default.css
329 ms
header-1.css
326 ms
default.css
328 ms
extralayers.css
348 ms
settings.css
435 ms
style.css
434 ms
teaser_glowinthedarkwicked-300x300.jpg
628 ms
jquery-2.1.4.min.js
627 ms
scripts.js
624 ms
app.js
620 ms
jquery.themepunch.tools.min.js
707 ms
jquery.themepunch.revolution.min.js
707 ms
demo.revolution_slider.js
621 ms
jquery.matchHeight-min.js
623 ms
jquery-jvectormap-2.0.3.min.js
722 ms
jquery-jvectormap-de-mill.js
748 ms
jquery-jvectormap-europe-mill.js
747 ms
gdp-data.js
746 ms
de.png
901 ms
gb.png
901 ms
logo_light.png
899 ms
1x1.png
901 ms
candy2o_full_650.jpg
1344 ms
goldplating_ad.jpg
1310 ms
40505152_uvls.jpg
2107 ms
createx-workshop-300x300.jpg
966 ms
banner_iwata_EN.png
1309 ms
ca01_1.jpg
1308 ms
cf01_1.jpg
1508 ms
sv01_1.jpg
1332 ms
me01_1.jpg
1661 ms
sm01_1.jpg
1528 ms
artool_logo_transp_klein.png
1441 ms
01.jpg
1439 ms
05.jpg
1446 ms
02.jpg
1258 ms
06.jpg
1303 ms
04.jpg
1324 ms
03.jpg
1335 ms
logo-footer.png
1306 ms
world-map.png
1326 ms
footer_sprite.png
1401 ms
mem8YaGs126MiZpBA-UFVZ0e.ttf
136 ms
mem5YaGs126MiZpBA-UN_r8OUuhs.ttf
185 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
169 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
185 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
183 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
190 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
184 ms
S6uyw4BMUTPHjx4wWw.ttf
191 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
187 ms
glyphicons-halflings-regular.woff
1181 ms
fontawesome-webfont.woff
1189 ms
font-icons.woff
1386 ms
bootstrap.min.js
1082 ms
loader.gif
1016 ms
revicons.woff
1107 ms
slider_02.jpg
1106 ms
slider_01.jpg
758 ms
owl.carousel.min.js
188 ms
createx.de accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
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
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.
createx.de 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
createx.de 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
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Createx.de can be misinterpreted by Google and other search engines. Our service has detected that English 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 Createx.de 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.
createx.de
Open Graph description is not detected on the main page of Createx. 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: