5.2 sec in total
1.4 sec
3.5 sec
317 ms
Click here to check amazing Jendo content. Otherwise, check out these important facts you probably never knew about jendo.de
Fanartikel, Vereinsbedarf, Souvenirartikel, Werbemittel - since 1991. Bei uns können Sie Ihren Verein, Ihre Stadt, Ihr Logo, Ihre Firma oder Ihren Spruch dauerhaft zur Geltung bringen.
Visit jendo.deWe analyzed Jendo.de page load time and found that the first response time was 1.4 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
jendo.de performance score
name
value
score
weighting
Value7.6 s
0/100
10%
Value9.1 s
1/100
25%
Value9.0 s
14/100
10%
Value170 ms
93/100
30%
Value0.379
28/100
15%
Value9.4 s
31/100
10%
1404 ms
23 ms
219 ms
33 ms
215 ms
Our browser made a total of 58 requests to load all elements on the main page. We found that 83% of them (48 requests) were addressed to the original Jendo.de, 5% (3 requests) were made to S.gravatar.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Jendo.de.
Page size can be reduced by 623.4 kB (26%)
2.4 MB
1.8 MB
In fact, the total size of Jendo.de main page is 2.4 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 71.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. 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 71.0 kB or 86% of the original size.
Potential reduce by 91.0 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. Jendo images are well optimized though.
Potential reduce by 170.1 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 170.1 kB or 63% of the original size.
Potential reduce by 291.3 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. Jendo.de needs all CSS files to be minified and compressed as it can save up to 291.3 kB or 77% of the original size.
Number of requests can be reduced by 34 (62%)
55
21
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jendo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
www.jendo.de
1404 ms
css
23 ms
font_customizer.min.css
219 ms
css
33 ms
style.css
215 ms
dashicons.min.css
420 ms
desktop_style.css
221 ms
cli-style.css
215 ms
fpu-front.min.css
425 ms
gc-front.min.css
531 ms
mc-front.min.css
325 ms
tc_common.min.css
721 ms
red.min.css
410 ms
style.css
429 ms
jquery.fancybox-1.3.4.min.css
536 ms
style.css
525 ms
jetpack.css
735 ms
jquery.js
839 ms
jquery-migrate.min.js
637 ms
front_end_script.js
645 ms
cookielawinfo.js
656 ms
fpu-front.min.js
750 ms
jquery.fancybox-1.3.4.min.js
759 ms
tc-scripts.min.js
873 ms
font-customizer-front.min.js
642 ms
qppr_frontend_script.min.js
671 ms
devicepx-jetpack.js
4 ms
gprofiles.js
55 ms
wpgroho.js
672 ms
holder.js
682 ms
core.min.js
672 ms
modernizr.min.js
672 ms
retina.min.js
752 ms
wp-embed.min.js
751 ms
e-201611.js
4 ms
Jendo_Logo_500x200.png
143 ms
NEU.png
142 ms
Aufnaeher.jpg
357 ms
Pins-1.jpg
363 ms
Schal-quer.jpg
373 ms
Trikot-V.jpg
286 ms
Pucks-1.jpg
253 ms
Stick-1.jpg
450 ms
fidele-haie-570x350.png
669 ms
Wappen.jpg
503 ms
jendo_de_Auto-C2-0031-570x350.jpg
502 ms
Drucksachen.png
501 ms
jendo_de_schluesselband002-500x350.jpg
502 ms
Textilienshop-570x174.png
673 ms
Fidele-Haie-Logo-570x350.jpg
602 ms
Haie_Supporter_Club_300x300.png
600 ms
overlay.png
609 ms
V86VyqXbc09Sss3BPsMj16CWcynf_cDxXwCLxiixG1c.ttf
79 ms
rxxXUYj4oZ6Q5oDJFtEd6i3USBnSvpkopQaUR-2r7iU.ttf
78 ms
genericons-regular-webfont.woff
550 ms
hovercard.css
27 ms
services.css
57 ms
g.gif
3 ms
jendo.de accessibility score
jendo.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
Browser errors were logged to the console
jendo.de SEO score
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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jendo.de can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Jendo.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.
jendo.de
Open Graph data is detected on the main page of Jendo. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: