27.3 sec in total
294 ms
26.4 sec
643 ms
Welcome to 1414.de homepage info - get ready to check 1414 best content for Germany right away, or after learning these important things about 1414.de
Haben SIE etwas fotografiert, das BILD drucken oder BILD.de veröffentlichen soll? Egal ob lustig, spektakulär, spannend oder kurios – die 1414-Redaktion ...
Visit 1414.deWe analyzed 1414.de page load time and found that the first response time was 294 ms and then it took 27 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
1414.de performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value6.7 s
7/100
25%
Value7.7 s
24/100
10%
Value720 ms
41/100
30%
Value0.038
100/100
15%
Value15.0 s
8/100
10%
294 ms
1152 ms
480 ms
1578 ms
290 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 72% of them (43 requests) were addressed to the original 1414.de, 5% (3 requests) were made to Cdn.krxd.net and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (20 sec) belongs to the original domain 1414.de.
Page size can be reduced by 977.0 kB (21%)
4.7 MB
3.7 MB
In fact, the total size of 1414.de main page is 4.7 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. 30% of websites need less resources to load. Images take 3.8 MB which makes up the majority of the site volume.
Potential reduce by 40.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. This page needs HTML code to be minified as it can gain 8.4 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 40.3 kB or 77% of the original size.
Potential reduce by 356.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. 1414 images are well optimized though.
Potential reduce by 358.0 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 358.0 kB or 65% of the original size.
Potential reduce by 221.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. 1414.de needs all CSS files to be minified and compressed as it can save up to 221.9 kB or 84% of the original size.
Number of requests can be reduced by 15 (28%)
54
39
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 1414. 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.
1414.de
294 ms
www.1414.de
1152 ms
application-d89c788826e91c165e5282df08182803.css
480 ms
modernizr-37aab4af4d5844c4338a63a3f2750fad.js
1578 ms
1765680693.js
290 ms
smartad_server-0e0303be8e7e8770489948e8753cd2d3.js
862 ms
application-51a3d66d6e16283c4398f5a36afcf28f.js
3466 ms
require-f678a4f1d9fa9316ffa2df9784a00d64.js
634 ms
controltag
125 ms
24062,24064,24066,24068
326 ms
krux_container.js
1119 ms
rta.js
70 ms
controltag.js.e0ce6829d34e23edb3c90f3615dd81e0
89 ms
app_install_page_bg-d076d32d704ca3e4319df806af1a4a9a.jpg
662 ms
app_install_page_landing_text-14a162dca43a9a84b9fe0a7a77472fad.png
262 ms
app_install_page_mobile_link-88fe772537711d5093e1eddbd9dd5024.png
262 ms
analytics.js
94 ms
ga.js
120 ms
a.js
1108 ms
wt
948 ms
de-xoz-videoplayer-core-bild-e3c5ac7382925f1236ffeea94017491d.js
614 ms
a.js
820 ms
8973130039
241 ms
ic_close_22x21_360-e2a855f317abdfd46762e70981916426.png
251 ms
logo_136x44-484f92ae4e81b7c3244c3b17d0d16e66.png
247 ms
sprite-afe3127ccade656fad60a63c87c2ba18.png
420 ms
landing_title-6775d7ce986a0106f40f91c00ef45bbf.png
1051 ms
collect
65 ms
notifications
257 ms
contents
2061 ms
missions
1523 ms
photos
989 ms
lp_photo_1cb04795595f890bf125d71df36f5a65_0.png
20030 ms
footer_app-store_mobile-0d13e264f2fe002da508fd6e1e510cb8.png
635 ms
footer_google-play_mobile-0dcdbf9180a6d37fb600cf11bdef5799.png
1062 ms
lp_photo_230135aa2c82f42dc3e825a805dadbdb_0.png
10949 ms
footer_fb_icon-a3d2a19a5c550db8e4f32b348619d53f.jpg
1254 ms
footer_twitter_icon-91d75693f6aad122f275673fdf7a2288.jpg
1553 ms
footer_pinterest_icon-c39b714200a489fe720c75252ee7a9d7.jpg
1566 ms
a.js
1211 ms
thumb_limit_296_76a09c09957a1dede877428e4dabca84.jpg
1202 ms
thumb_limit_296_b5a080d981a68164014d841d6bcd3c6a.jpg
1069 ms
thumb_limit_296_66170e3f75e0f6d9d22a8ae3c8257108.jpg
1040 ms
thumb_limit_296_62651ba88e9f924a11ec41fcae9e34ee.jpg
1445 ms
thumb_limit_296_57f6ac2eab54522c9990e282331bc02f.jpg
2005 ms
thumb_limit_296_9a51882e98fb66c7eee9cf9cdf6b4a3a.jpg
1839 ms
thumb_limit_296_3f4db2f00c0e91d4569e949bb31faf8c.jpg
1823 ms
thumb_limit_296_ad7067309028575a000cfc4889267032.jpg
1921 ms
a.jpg
767 ms
thumb_fill_640x220_559cd70ebf67be791bc4d69d5a1ce0f3_header_image_1459763092.jpg
3123 ms
ic_laufzeit_60x50-ecdc6385563a068c8281b755ebdfbec2.png
1527 ms
ic_gewinn_60x50-d5d0195f29b61c11571c105bb7d2b6fd.png
1690 ms
thumb_fill_640x220_2d383778ad448aede0d4442199e97169_header_image_1441888916.jpg
2730 ms
thumb_fill_640x220_f6484aa06a4abd4cb11e001c25208c50_header_image_1458040368.jpg
3404 ms
about_community-806991707fab6a51586eaff05b10d546.png
1422 ms
about_leserreporter-c9a4bc5c263fee7ca1e60d3573675b1e.png
2035 ms
about_missions-01b25612aaeb862a505e68c38bd2b01b.png
2455 ms
nr-918.min.js
234 ms
optout_check
172 ms
get
125 ms
1414.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.
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
<frame> or <iframe> elements do not have a title
1414.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
1414.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 1414.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 1414.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.
1414.de
Open Graph data is detected on the main page of 1414. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: