2.5 sec in total
120 ms
1.7 sec
693 ms
Visit freshme.de now to see the best up-to-date FRESHME content for Germany and also check out these interesting facts you probably never knew about freshme.de
Visit freshme.deWe analyzed Freshme.de page load time and found that the first response time was 120 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
freshme.de performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value12.2 s
0/100
25%
Value8.6 s
17/100
10%
Value1,670 ms
11/100
30%
Value0
100/100
15%
Value12.5 s
14/100
10%
120 ms
226 ms
12 ms
78 ms
70 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 91% of them (67 requests) were addressed to the original Freshme.de, 3% (2 requests) were made to Res.brandwire.tv and 1% (1 request) were made to Reswww.freshme.de. The less responsive or slowest element that took the longest time to load (705 ms) relates to the external source Script.ioam.de.
Page size can be reduced by 81.4 kB (6%)
1.4 MB
1.3 MB
In fact, the total size of Freshme.de main page is 1.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. 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 68.4 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 13.2 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 68.4 kB or 81% of the original size.
Potential reduce by 10.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. FRESHME images are well optimized though.
Potential reduce by 1.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. This website has mostly compressed JavaScripts.
Potential reduce by 1.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. Freshme.de has all CSS files already compressed.
Number of requests can be reduced by 32 (48%)
67
35
The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FRESHME. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
freshme.de
120 ms
www.freshme.de
226 ms
font.css
12 ms
style.min.css
78 ms
instagram-dsgvo.css
70 ms
magazine-player.min.css
91 ms
js_composer.min.css
201 ms
style.css
93 ms
packages.min.css
174 ms
style.css
123 ms
tana-fork.css
231 ms
instagram-dsgvo.js
148 ms
magazine-player.es5.min.js
266 ms
freshme.min.js
199 ms
jquery.js
265 ms
jquery-migrate.min.js
229 ms
mediaelement-and-player.min.js
411 ms
mediaelement-migrate.min.js
265 ms
twik_css
114 ms
style.css
262 ms
tcs.js
56 ms
style.css
407 ms
font-awesome.min.css
465 ms
flexslider.min.css
463 ms
prettyPhoto.min.css
465 ms
wp-mediaelement.min.js
465 ms
packages.min.js
467 ms
core.min.js
466 ms
widget.min.js
466 ms
mouse.min.js
467 ms
slider.min.js
468 ms
scripts.min.js
581 ms
wp-embed.min.js
466 ms
js_composer_front.min.js
579 ms
jquery.flexslider-min.js
579 ms
jquery.prettyPhoto.min.js
581 ms
font.css
5 ms
font.css
5 ms
5c19030a259a5.css
102 ms
freshme_logo_header.png
124 ms
pattern-en.png
124 ms
parfum-sommer.jpg
125 ms
dessous-trend-sommer.jpg
127 ms
deko-balkon-sommer.jpg
124 ms
freshme_shopthelook_teaser_homepage.jpg
126 ms
beauty_blog-600x600.jpg
232 ms
iStock-576926776-600x600.jpg
233 ms
Blusen-Sommer-800x386.jpg
234 ms
eco-label-deutschland-dessous-800x386.jpg
237 ms
schuh-trends-800x386.jpg
235 ms
5x3.png
234 ms
Rosie-Huntington.jpg
349 ms
16x7.png
235 ms
Amy-Schumer-Baby.jpg
353 ms
kate-schwanger.jpg
352 ms
arrow-right.png
350 ms
beauty-tipps-skandi-600x600.jpg
354 ms
4x3.png
351 ms
tonerde-tipps-1-600x600.jpg
354 ms
beauty-produkte-angesagt-600x600.jpg
356 ms
beauty-produkte-sommer-600x600.jpg
412 ms
Rosie-Huntington-80x80.jpg
354 ms
Amy-Schumer-Baby-80x80.jpg
352 ms
SF-UI-Display-Regular.otf
290 ms
SF-UI-Display-Medium.otf
325 ms
SF-UI-Display-Light.otf
597 ms
SF-UI-Display-Thin.otf
596 ms
SF-UI-Display-Ultralight.otf
326 ms
SF-UI-Display-Semibold.otf
598 ms
SF-UI-Display-Bold.otf
600 ms
SF-UI-Display-Heavy.otf
602 ms
SF-UI-Display-Black.otf
603 ms
fontawesome-webfont.woff
600 ms
iam.js
705 ms
freshme.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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
freshme.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
Missing source maps for large first-party JavaScript
freshme.de SEO score
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 Freshme.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 Freshme.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.
freshme.de
Open Graph description is not detected on the main page of FRESHME. 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: