3.7 sec in total
667 ms
2.4 sec
638 ms
Click here to check amazing JFFH content for Germany. Otherwise, check out these important facts you probably never knew about jffh.de
Filmfestival in Hamburg. Japanisches Kino mit Welt-, Europa- und Deutschlandpremieren
Visit jffh.deWe analyzed Jffh.de page load time and found that the first response time was 667 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
jffh.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value13.9 s
0/100
25%
Value6.2 s
43/100
10%
Value380 ms
70/100
30%
Value0
100/100
15%
Value12.9 s
13/100
10%
667 ms
178 ms
271 ms
270 ms
271 ms
Our browser made a total of 65 requests to load all elements on the main page. We found that 77% of them (50 requests) were addressed to the original Jffh.de, 6% (4 requests) were made to Blog.jffh.de and 5% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (797 ms) relates to the external source Blog.jffh.de.
Page size can be reduced by 681.3 kB (46%)
1.5 MB
815.6 kB
In fact, the total size of Jffh.de main page is 1.5 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. Javascripts take 584.2 kB which makes up the majority of the site volume.
Potential reduce by 17.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 17.3 kB or 70% of the original size.
Potential reduce by 24.1 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. JFFH images are well optimized though.
Potential reduce by 385.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 385.7 kB or 66% of the original size.
Potential reduce by 254.2 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. Jffh.de needs all CSS files to be minified and compressed as it can save up to 254.2 kB or 83% of the original size.
Number of requests can be reduced by 41 (66%)
62
21
The browser has sent 62 CSS, Javascripts, AJAX and image requests in order to completely render the main page of JFFH. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
www.jffh.de
667 ms
screen.css
178 ms
style.css
271 ms
mootools.v1.11.js
270 ms
jd.gallery.js
271 ms
functions.js
181 ms
jquery.js
448 ms
styles.css
265 ms
esdc-dp.css
359 ms
esdc-custom.css
354 ms
orgSeries.css
358 ms
jquery.js
536 ms
jquery-migrate.min.js
357 ms
esdc.js
444 ms
shutter-reloaded.css
446 ms
shutter-reloaded.js
366 ms
jquery.form.min.js
366 ms
scripts.js
453 ms
core.min.js
454 ms
datepicker.min.js
611 ms
wp-embed.min.js
454 ms
reset.css
366 ms
typography.css
453 ms
grid.css
452 ms
forms.css
453 ms
wp-emoji-release.min.js
227 ms
JFFH-Team-2015-DANKE.jpg
797 ms
BA86aPdPGJg
96 ms
Video-JFFH-2015.jpg
605 ms
Publikum3.jpg
696 ms
Sponsoren-JFFH-2015.jpg
609 ms
bg_tile.jpg
107 ms
jffhlogo_quer.png
435 ms
li.png
107 ms
Ame%20und%20Yuki_600px.jpg
434 ms
Die%20Legende%20der%20Prinzessin%20Kaguya_600px.jpg
106 ms
JFFH-2015-Foto-Programmhefte-225x300.jpg
442 ms
de.png
430 ms
gb.png
429 ms
jp.png
432 ms
icon_facebook.png
442 ms
icon_twitter.png
448 ms
icon_flickr.png
484 ms
search_grey.gif
485 ms
Sponsorenleiste.png
497 ms
close.gif
471 ms
prev.gif
471 ms
prev-d.gif
471 ms
next.gif
474 ms
next-d.gif
475 ms
resize1.gif
481 ms
resize2.gif
481 ms
resize-d.gif
480 ms
loading.gif
545 ms
like.php
428 ms
www-embed-player-vflfNyN_r.css
33 ms
www-embed-player.js
72 ms
base.js
221 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
77 ms
ad_status.js
91 ms
qeKvIRsJabD.js
87 ms
LVx-xkvaJ0b.png
88 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
73 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
76 ms
print.css
93 ms
jffh.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
Links do not have a discernible name
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.
jffh.de 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
jffh.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
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jffh.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 Jffh.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.
jffh.de
Open Graph description is not detected on the main page of JFFH. 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: