5.9 sec in total
1.7 sec
3.9 sec
272 ms
Visit forever25.de now to see the best up-to-date Forever25 content for Germany and also check out these interesting facts you probably never knew about forever25.de
Visit forever25.deWe analyzed Forever25.de page load time and found that the first response time was 1.7 sec and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
forever25.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.9 s
53/100
25%
Value9.4 s
12/100
10%
Value700 ms
42/100
30%
Value0.01
100/100
15%
Value14.3 s
9/100
10%
1681 ms
726 ms
828 ms
1110 ms
928 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that all of those requests were addressed to Forever25.de and no external sources were called. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Forever25.de.
Page size can be reduced by 64.9 kB (14%)
460.3 kB
395.4 kB
In fact, the total size of Forever25.de main page is 460.3 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 413.2 kB which makes up the majority of the site volume.
Potential reduce by 41.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 4.9 kB, which is 11% 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 41.0 kB or 88% of the original size.
Potential reduce by 23.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. Forever25 images are well optimized though.
Potential reduce by 425 B
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 425 B or 75% of the original size.
Number of requests can be reduced by 20 (43%)
47
27
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forever25. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
forever25.de
1681 ms
gm_dynamic.css.php
726 ms
flag.png
828 ms
var5_logo.jpg
1110 ms
icon-grey-basket-big.png
928 ms
icon-grey-arrowdown.png
925 ms
table.gif
931 ms
628t.jpg
1129 ms
img_4050.jpg
935 ms
img_4074.jpg
1037 ms
img_4070.jpg
1044 ms
img_4054.jpg
1047 ms
lw007a.jpg
1042 ms
skre8e.jpg
1140 ms
kd-205_1.jpg
1149 ms
img_9261.jpg
1153 ms
img_9262.jpg
1156 ms
img_9310.jpg
1204 ms
steriliz__.jpg
1232 ms
kd3060-.jpg
1242 ms
kd-s611.jpg
1253 ms
img_4046.jpg
1263 ms
0107b.jpg
1260 ms
gm_javascript.js.php
2183 ms
GMCounter.js
1247 ms
hs_nider_beutel.jpg
1263 ms
item_ltr.gif
1268 ms
icon_arrow.gif
1278 ms
diggs.gif
1276 ms
folkd.gif
1348 ms
favoriten.gif
1365 ms
google.gif
1370 ms
delicio.gif
1375 ms
edelight.gif
1378 ms
bcg5.jpg
1219 ms
gradient-reflection.png
825 ms
icon-white-home.png
831 ms
icon-white-arrowdown.png
822 ms
gradient.png
757 ms
separator-30-vert.png
746 ms
gradient-small-reverse.png
751 ms
button-left.png
747 ms
button-right.png
750 ms
article-item-bg.gif
739 ms
separator-dotted-hori.png
735 ms
icon-grey-circlearrowrigh.png
732 ms
dropdown-shopping-cart-bottom-bg.png
742 ms
flag.png
778 ms
forever25.de 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
Image elements do not have [alt] attributes
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.
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA IDs are not unique
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.
forever25.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
Missing source maps for large first-party JavaScript
forever25.de SEO score
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 Forever25.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 Forever25.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.
forever25.de
Open Graph description is not detected on the main page of Forever25. 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: