11.6 sec in total
1 sec
10.1 sec
423 ms
Welcome to freestring.de homepage info - get ready to check Freestring best content right away, or after learning these important things about freestring.de
This website is for sale! lupe.at is your first and best source for all of the information you’re looking for. From general topics to more of what you would expect to find here, lupe.at has it all. We...
Visit freestring.deWe analyzed Freestring.de page load time and found that the first response time was 1 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
freestring.de performance score
name
value
score
weighting
Value2.9 s
52/100
10%
Value3.4 s
66/100
25%
Value3.8 s
84/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.9 s
96/100
10%
1045 ms
303 ms
205 ms
187 ms
188 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 18% of them (20 requests) were addressed to the original Freestring.de, 15% (17 requests) were made to Speed-s.pointroll.com and 7% (8 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Topblogs.de.
Page size can be reduced by 339.8 kB (48%)
714.4 kB
374.6 kB
In fact, the total size of Freestring.de main page is 714.4 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. 60% of websites need less resources to load. Javascripts take 343.1 kB which makes up the majority of the site volume.
Potential reduce by 50.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 9.1 kB, which is 15% 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 50.0 kB or 82% of the original size.
Potential reduce by 3.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. Freestring images are well optimized though.
Potential reduce by 202.6 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 202.6 kB or 59% of the original size.
Potential reduce by 83.4 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. Freestring.de needs all CSS files to be minified and compressed as it can save up to 83.4 kB or 85% of the original size.
Number of requests can be reduced by 72 (68%)
106
34
The browser has sent 106 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Freestring. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
www.freestring.de
1045 ms
style.css
303 ms
default.css
205 ms
widget.css
187 ms
twitter-feed.css
188 ms
jetpack.css
384 ms
show_ads.js
4 ms
devicepx-jetpack.js
6 ms
wp-embed.min.js
105 ms
e-201611.js
4 ms
wp-emoji-release.min.js
215 ms
logo.png
104 ms
tracker.php
7479 ms
wallpaper-bg.jpg
435 ms
header-bg.jpg
434 ms
ca-pub-0312997416821799.js
172 ms
zrt_lookup.html
424 ms
show_ads_impl.js
95 ms
nav-bar-bg.jpg
408 ms
button-bg.jpg
408 ms
cat-bar-bg.jpg
407 ms
rss-cyan.gif
407 ms
rss-orange.gif
425 ms
comment-bg.jpg
402 ms
zanox.js
383 ms
imp
378 ms
imp
365 ms
widget-heading-bg.jpg
371 ms
footer-bg.jpg
369 ms
subfooter-bg.jpg
368 ms
ads
287 ms
banner-mug5-300x250-de.jpg
590 ms
gutschein_300x250.gif
645 ms
m_js_controller.js
73 ms
abg.js
105 ms
osd.js
58 ms
g.gif
74 ms
828165540468099647DA
282 ms
ads
219 ms
favicon
111 ms
googlelogo_color_112x36dp.png
108 ms
nessie_icon_tiamat_white.png
85 ms
s
61 ms
x_button_blue2.png
51 ms
ads
235 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
58 ms
6959990728735488434
37 ms
s_0RpkkOZZhN_719439273.html
54 ms
dvbs_src.js
45 ms
dvtp_src.js
127 ms
creative_add_on.js
156 ms
verify.js
48 ms
38 ms
dvtp_src.js
4 ms
dvtp_src.js
5 ms
bst2tv3.html
34 ms
gutschein_300x250.gif
733 ms
305 ms
dvtp_src_internal26.js
6 ms
surly.js
318 ms
t2tv7.html
293 ms
visit.js
255 ms
visit.js
210 ms
visit.js
115 ms
prWriteCode.js
149 ms
ba.html
19 ms
4.gif
28 ms
2532.js
6 ms
avs5639.js
8 ms
event.jpg
136 ms
query.js
83 ms
event.gif
132 ms
event.gif
114 ms
event.gif
114 ms
event.gif
113 ms
event.jpg
125 ms
event.gif
121 ms
B9307628.126437961;dc_trk_aid=300411737;dc_trk_cid=67811946;ord=0.3099254039116204
83 ms
K61275_FL_MY16_LDA_Command_More_300x250.jpg
86 ms
PRScript
52 ms
query.js
60 ms
event.gif
25 ms
box_19_top-right.png
11 ms
ci.png
9 ms
activeview
12 ms
activeview
34 ms
5 ms
K61275_FL_MY16_LDA_Command_More_300x250.html
41 ms
EBLoader.js
15 ms
easeljs-0.8.1.min.js
124 ms
tweenjs-0.6.1.min.js
25 ms
movieclip-0.8.1.min.js
27 ms
preloadjs-0.6.1.min.js
24 ms
K61275_FL_MY16_LDA_Command_More_300x250.js
15 ms
activeview
12 ms
prTrk.js
12 ms
bg.jpg
21 ms
car1.png
15 ms
car1_shadow.png
14 ms
car2.png
12 ms
car3.png
12 ms
copy1.png
32 ms
copy2.png
13 ms
copy3.png
12 ms
copy4.png
13 ms
copy_cta.png
12 ms
legal.png
12 ms
logo.png
17 ms
851398
231 ms
ui
55 ms
event.jpg
28 ms
freestring.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
Form elements do not have associated labels
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.
freestring.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
freestring.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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 doesn't use legible font sizes
Tap targets are not sized appropriately
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freestring.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Freestring.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.
freestring.de
Open Graph data is detected on the main page of Freestring. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: