12.9 sec in total
538 ms
10.3 sec
2.1 sec
Click here to check amazing ROXIVE content for Germany. Otherwise, check out these important facts you probably never knew about roxive.de
ROXIVE – RESPONSIVE OXID ESHOP THEME - „RoxIVE“ ist ein Responsive Theme für den OXID eShop, welches auf den aktuellsten Techniken der Web-Entwicklung basiert.Dadurch wird Ihr Shop auf allen Endgeräte
Visit roxive.deWe analyzed Roxive.de page load time and found that the first response time was 538 ms and then it took 12.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
roxive.de performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value2.2 s
94/100
25%
Value3.6 s
87/100
10%
Value330 ms
76/100
30%
Value0.015
100/100
15%
Value5.0 s
77/100
10%
538 ms
1436 ms
236 ms
42 ms
268 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Roxive.de, 72% (54 requests) were made to Digidesk.de and 12% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.7 sec) relates to the external source Digidesk.de.
Page size can be reduced by 1.8 MB (62%)
2.9 MB
1.1 MB
In fact, the total size of Roxive.de main page is 2.9 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. CSS take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 73.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. This page needs HTML code to be minified as it can gain 35.9 kB, which is 43% 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 73.0 kB or 87% of the original size.
Potential reduce by 6.5 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. ROXIVE images are well optimized though.
Potential reduce by 682.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 682.7 kB or 67% of the original size.
Potential reduce by 1.1 MB
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. Roxive.de needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 89% of the original size.
Number of requests can be reduced by 48 (77%)
62
14
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ROXIVE. 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 20 to 1 for CSS and as a result speed up the page load time.
roxive.de
538 ms
1436 ms
shariff.complete.css
236 ms
css
42 ms
mediaelementplayer.min.css
268 ms
wp-mediaelement.css
280 ms
layerslider.css
277 ms
layerslider.custom.css
288 ms
css
68 ms
styles.css
288 ms
style.css
530 ms
shariff.min.local.css
566 ms
woocommerce-gzd-layout.min.css
567 ms
chosen.css
574 ms
frontend.css
578 ms
js_composer.min.css
2135 ms
bundles-style.css
919 ms
jquery.js
1064 ms
jquery-migrate.min.js
1250 ms
greensock.js
1536 ms
layerslider.kreaturamedia.jquery.js
1692 ms
layerslider.transitions.js
2535 ms
add-to-cart.min.js
1905 ms
woocommerce-add-to-cart.js
1996 ms
iframeResizer.min.js
2046 ms
iframeResizer.contentWindow.min.js
2266 ms
initial.css
2348 ms
www.digidesk.de
2842 ms
www.digidesk.de
2926 ms
Open%20Sans.css
2529 ms
initial.js
4055 ms
emos2.js
3396 ms
shariff.complete.js
4090 ms
mediaelement-and-player.min.js
4047 ms
wp-mediaelement.js
3391 ms
jquery.form.min.js
3392 ms
scripts.js
3609 ms
jquery.blockUI.min.js
3607 ms
woocommerce.min.js
3661 ms
js
86 ms
jquery.cookie.min.js
4042 ms
cart-fragments.min.js
3800 ms
isotope.pkgd.min.js
3800 ms
comment-reply.min.js
4095 ms
js_composer_front.min.js
4086 ms
select2.min.js
4084 ms
wp-embed.min.js
4139 ms
wp-emoji-release.min.js
4170 ms
logo_qards_light-300x101-49334.png
2113 ms
resp_note-500x500-96952.jpg
3736 ms
responsive_oldpc-545x426-86887.jpg
3054 ms
roxive_landing_header-2600x1322-21296.jpg
5721 ms
3QfhjbGquSo
491 ms
roxive_black_header-2400x923-13774.jpg
4145 ms
typewriter-350x200-69207.jpg
2888 ms
pencil-350x200-68760.jpg
2748 ms
clock-350x200-98571.jpg
2886 ms
IdzUBXauiTk
153 ms
YYzH0-uEl5I
138 ms
MTP_ySUJH_bn48VBG8sNSha1RVmPjeKy21_GQJaLlJI.woff
39 ms
k3k702ZOKiLJc3WVjuplzBa1RVmPjeKy21_GQJaLlJI.woff
56 ms
EInbV5DfGHOiMmvb1Xr-hha1RVmPjeKy21_GQJaLlJI.woff
120 ms
OpenSans-Regular.woff
3359 ms
u-WUoqrET9fUeobQW7jkRT8E0i7KZn-EPnyo3HZu7kw.woff
122 ms
DXI1ORHCpsQm3Vp6mXoaTRa1RVmPjeKy21_GQJaLlJI.woff
121 ms
xjAJXh38I15wypJXxuGMBtIh4imgI8P11RFo6YPCPC0.woff
120 ms
PRmiXeptR36kaC0GEAetxrsuoFAk0leveMLeqYtnfAY.woff
121 ms
www-embed-player-vfl-z2BtK.css
157 ms
www-embed-player.js
207 ms
base.js
365 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
482 ms
ad_status.js
480 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
1478 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
1479 ms
1906 ms
roxive.de 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.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
roxive.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
Page has valid source maps
roxive.de 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
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
DE
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Roxive.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it does not match the claimed English language. Our system also found out that Roxive.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.
roxive.de
Open Graph data is detected on the main page of ROXIVE. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: