5.4 sec in total
324 ms
3.5 sec
1.5 sec
Welcome to odice.nl homepage info - get ready to check Odice best content right away, or after learning these important things about odice.nl
Fahrräder, Trekkingräder, E-Bikes & Citybikes aus Oldenburg. Die cycle union bietet vier Fahrradmarke unter einem Dach.
Visit odice.nlWe analyzed Odice.nl page load time and found that the first response time was 324 ms and then it took 5.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
odice.nl performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value6.5 s
9/100
25%
Value12.1 s
3/100
10%
Value890 ms
32/100
30%
Value0.272
45/100
15%
Value16.6 s
5/100
10%
324 ms
95 ms
214 ms
461 ms
501 ms
Our browser made a total of 115 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Odice.nl, 31% (36 requests) were made to Google.com and 11% (13 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (994 ms) relates to the external source Cycle-union.de.
Page size can be reduced by 842.6 kB (15%)
5.6 MB
4.7 MB
In fact, the total size of Odice.nl main page is 5.6 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. 80% 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.5 MB which makes up the majority of the site volume.
Potential reduce by 35.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 35.3 kB or 84% of the original size.
Potential reduce by 50.8 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. Odice images are well optimized though.
Potential reduce by 611.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 611.5 kB or 69% of the original size.
Potential reduce by 144.9 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. Odice.nl needs all CSS files to be minified and compressed as it can save up to 144.9 kB or 86% of the original size.
Number of requests can be reduced by 15 (14%)
104
89
The browser has sent 104 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Odice. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
www.cycle-union.com
324 ms
de
95 ms
214 ms
screen.css
461 ms
main.js
501 ms
analytics.js
90 ms
embed
293 ms
cu-logo.svg
269 ms
header_start.jpg
282 ms
trans.png
274 ms
stoerer-fahrradregistrierung.png
274 ms
02_kachel_640x534.jpg
306 ms
tests_640x534.jpg
388 ms
03_kachel_640x534.jpg
275 ms
welt.png
387 ms
screen.png
683 ms
ebm_ebike_13zehn_mg_8232_web.jpg
397 ms
ebm-logo.svg
336 ms
vsf-logo.svg
396 ms
kreidler-logo.svg
484 ms
rabeneick-logo.svg
492 ms
content_slides_1.jpg
681 ms
cycleunion_news_eurobike.jpg
602 ms
cycleunion_news_ebike.jpg
610 ms
culogo.jpg
604 ms
21_04_15_trio_for_rio_rad_zu_olympia_01.jpg
794 ms
01_04_15_kreidler_werksteam_2015_leidenschaft_rennsport_01.jpg
609 ms
content_slider_1920_5.jpg
674 ms
content_slider_rabeneick01.jpg
994 ms
cu-logo-plain.svg
783 ms
Lato-Light.woff
872 ms
Lato-Regular.woff
941 ms
Lato-LightItalic.woff
941 ms
icons.woff
827 ms
collect
190 ms
2_cu_slider_rabeneick3.jpg
901 ms
ebm_ebike_allgemein_mg_7821_web.jpg
743 ms
content_slides_7.jpg
790 ms
06_02_15_kreidler_vitality_eco_8_edition.jpg
818 ms
content_slider_1920_6.jpg
816 ms
content_slider_rabeneick03.jpg
823 ms
js
81 ms
init_embed.js
37 ms
common.js
72 ms
map.js
73 ms
google4.png
29 ms
overlay.js
27 ms
util.js
134 ms
onion.js
131 ms
search_impl.js
132 ms
stats.js
64 ms
openhand_8_8.cur
51 ms
ViewportInfoService.GetViewportInfo
66 ms
ViewportInfoService.GetViewportInfo
57 ms
transparent.png
53 ms
kh
168 ms
kh
246 ms
controls.js
103 ms
ViewportInfoService.GetViewportInfo
61 ms
vt
131 ms
vt
116 ms
vt
116 ms
vt
112 ms
vt
109 ms
vt
109 ms
vt
154 ms
vt
153 ms
vt
151 ms
vt
152 ms
vt
150 ms
vt
153 ms
vt
217 ms
vt
219 ms
vt
218 ms
vt
215 ms
vt
216 ms
vt
218 ms
vt
219 ms
vt
222 ms
vt
219 ms
vt
220 ms
vt
222 ms
vt
220 ms
vt
264 ms
vt
265 ms
vt
264 ms
vt
264 ms
vt
263 ms
vt
263 ms
vt
286 ms
vt
289 ms
vt
287 ms
vt
297 ms
vt
286 ms
css
122 ms
entity11.png
55 ms
mapcnt6.png
29 ms
tmapctrl.png
47 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
48 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
49 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
53 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
53 ms
ebm_ebike_13zehn_mg_8231_web.jpg
97 ms
content_slides_4.jpg
96 ms
content_slider_1920_5-1.jpg
99 ms
13_01_15_vabene_pro_rabeneick.jpg
102 ms
content_slider_rabeneick02.jpg
184 ms
AuthenticationService.Authenticate
15 ms
ebm_ebike_allgemein_mg_7889_web.jpg
94 ms
content_slides_6.jpg
96 ms
ebm_slider.jpg
94 ms
08_01_15_sherpa_lite_pro_rabeneick.jpg
97 ms
cu_slider_kreidler5.jpg
94 ms
06_01_15_rabeneick_rad_niagara.jpg
96 ms
01_04_15_kreidler_e_bike_tour_2015.jpg
97 ms
odice.nl 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
Form elements do not have associated labels
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
odice.nl 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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
odice.nl SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Odice.nl can be misinterpreted by Google and other search engines. Our service has detected that German 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 Odice.nl 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.
odice.nl
Open Graph description is not detected on the main page of Odice. 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: