9.5 sec in total
2.6 sec
6.3 sec
571 ms
Welcome to geoflags.de homepage info - get ready to check Geoflags best content for Germany right away, or after learning these important things about geoflags.de
Hamburg, Berlin, Paris, London, New York - entdecke über 1 Mio. Restaurants, Hotels, Bars, Sehenswürdigkeiten und weitere interessante Orte weltweit.
Visit geoflags.deWe analyzed Geoflags.de page load time and found that the first response time was 2.6 sec and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
geoflags.de performance score
2612 ms
34 ms
158 ms
629 ms
522 ms
Our browser made a total of 202 requests to load all elements on the main page. We found that 10% of them (21 requests) were addressed to the original Geoflags.de, 15% (31 requests) were made to Maps.google.com and 13% (27 requests) were made to S0.2mdn.net. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Geoflags.de.
Page size can be reduced by 766.0 kB (41%)
1.9 MB
1.1 MB
In fact, the total size of Geoflags.de main page is 1.9 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. 75% 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. Javascripts take 965.9 kB which makes up the majority of the site volume.
Potential reduce by 117.5 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 117.5 kB or 83% of the original size.
Potential reduce by 13.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. Geoflags images are well optimized though.
Potential reduce by 610.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 610.7 kB or 63% of the original size.
Potential reduce by 24.6 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. Geoflags.de needs all CSS files to be minified and compressed as it can save up to 24.6 kB or 79% of the original size.
Number of requests can be reduced by 105 (60%)
175
70
The browser has sent 175 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Geoflags. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 56 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
www.geoflags.de
2612 ms
jquery.min.js
34 ms
maps
158 ms
javascript_1294046745.js
629 ms
styles.css
522 ms
all.js
72 ms
show_ads.js
8 ms
getads.js
12 ms
de.js
272 ms
buttons.png
476 ms
hamburg1.jpg
480 ms
newflag.png
329 ms
loading.gif
326 ms
tgFCHqPI6MEaC2kzGEP9.JPG
730 ms
RxchER5KT1FRUzuVdPC9.jpg
730 ms
KK7HzCMnXcgZphOkApdU.jpg
729 ms
IO9bttCblmKhC3oYzrQT.jpg
729 ms
234 ms
ca-pub-9956806203996447.js
301 ms
zrt_lookup.html
306 ms
show_ads_impl.js
173 ms
toggle_up.png
218 ms
xd_arbiter.php
185 ms
xd_arbiter.php
273 ms
bg_box_grey.jpg
273 ms
bg_box_grey.png
264 ms
t.js
222 ms
ads
190 ms
osd.js
35 ms
l40XXU0N5mi2O9FOuv4f.JPG
478 ms
css
29 ms
m_js_controller.js
4 ms
abg.js
10 ms
favicon
61 ms
nessie_icon_tiamat_white.png
39 ms
s
37 ms
googlelogo_color_112x36dp.png
31 ms
x_button_blue2.png
24 ms
impr
141 ms
RxchER5KT1FRUzuVdPC9.jpg
135 ms
tgFCHqPI6MEaC2kzGEP9.JPG
482 ms
KK7HzCMnXcgZphOkApdU.jpg
256 ms
IO9bttCblmKhC3oYzrQT.jpg
242 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
5 ms
cJZKeOuBrn4kERxqtaUH3bO3LdcAZYWl9Si6vvxL-qU.woff
83 ms
adex.js
304 ms
rtb
118 ms
match
100 ms
0RZuyPGDOX_1047656624.html
8 ms
cl
58 ms
creative_add_on.js
78 ms
html_inpage_rendering_lib_200_120.js
38 ms
cms-2c.html
92 ms
loadImages.js
43 ms
2964
110 ms
Pug
62 ms
rum
43 ms
sync
42 ms
t.js
124 ms
t.js
196 ms
pixel
145 ms
tab_over_right.jpg
163 ms
sub_pfeil.jpg
312 ms
toggle_down.png
311 ms
tab_right.jpg
310 ms
0
154 ms
rs
88 ms
demconf.jpg
72 ms
tap.php
68 ms
rum
82 ms
385636.gif
51 ms
impr
145 ms
sd
61 ms
nuggad
195 ms
check
63 ms
m.gif
41 ms
pixel.gif
89 ms
analytic.js
120 ms
185 ms
1.gif
249 ms
match-result
56 ms
m_yahoo.gif
6 ms
rtb
176 ms
164 ms
rs.js
202 ms
lidar.js
87 ms
index.html
81 ms
gwdpage_style.css
126 ms
gwdattached_style.css
173 ms
gwdimage_style.css
172 ms
gwddoubleclick_style.css
172 ms
gwdpagedeck_style.css
173 ms
googbase_min.js
143 ms
gwd_webcomponents_min.js
161 ms
gwdpage_min.js
174 ms
gwdpagedeck_min.js
180 ms
Enabler_01_102.js
184 ms
gwddoubleclick_min.js
180 ms
gwdimage_min.js
177 ms
gwd-events-support.1.0.js
178 ms
gwdgpadataprovider_min.js
206 ms
gwdattached_min.js
209 ms
gwdtexthelper_min.js
208 ms
gwddatabinder_min.js
210 ms
gwdimagebutton_min.js
209 ms
pixel
153 ms
redirect
264 ms
activeview
113 ms
pixel
119 ms
redirect
225 ms
ads
323 ms
impr
184 ms
rpc.flow
126 ms
vce_st.js
79 ms
cm.gif
124 ms
2.gif
111 ms
cm.gif
102 ms
p2
58 ms
AvenirNextLTPro-Regular.woff
29 ms
AvenirNextLTProUltLtCn.woff
30 ms
p
28 ms
2.gif
94 ms
2.gif
96 ms
2.gif
96 ms
redirect
463 ms
rtb
130 ms
redirect
458 ms
728x90_logo.png
10 ms
728x90_btn.png
13 ms
23720825_20160120024305121_728x90_teaser_familia_4.jpg
5 ms
23720825_20160120024258770_728x90_teaser_familia_2.jpg
10 ms
23720825_20160114044413908_728x90_teaser_familia_1.jpg
5 ms
activeview
36 ms
220
149 ms
HH_Kop_160x600.html
16 ms
ga.js
31 ms
exitapi-impl.js
2 ms
addata.js
4 ms
edge.6.0.0.min.js
10 ms
HH_Kop_160x600_edge.js
72 ms
common.js
58 ms
map.js
58 ms
overlay.js
57 ms
util.js
54 ms
marker.js
54 ms
gallery.js
259 ms
HH_Kop_160x600_edge.js
56 ms
onion.js
32 ms
openhand_8_8.cur
176 ms
like.php
265 ms
like.php
251 ms
ViewportInfoService.GetViewportInfo
249 ms
stats.js
76 ms
controls.js
83 ms
infowindow.js
70 ms
dest.jpg
62 ms
text1.png
14 ms
pers.jpg
16 ms
text2.png
15 ms
preisButt.png
17 ms
ogilvyButt.png
14 ms
shine.png
14 ms
DB_15px.png
15 ms
css
28 ms
transparent.png
98 ms
2.gif
187 ms
2.gif
192 ms
fy8tT2klpgR.js
228 ms
google4.png
106 ms
mapcnt6.png
106 ms
sv5.png
107 ms
LVx-xkvaJ0b.png
223 ms
881
182 ms
CrYjSnGjrRCn0pd9VQsnFOvvDin1pK8aKteLpeZ5c0A.woff
79 ms
RxZJdnzeo3R5zSexge8UUbO3LdcAZYWl9Si6vvxL-qU.woff
81 ms
Hgo13k-tfSpn0qi1SFdUfbO3LdcAZYWl9Si6vvxL-qU.woff
82 ms
d-6IYplOFocCacKzxwXSOLO3LdcAZYWl9Si6vvxL-qU.woff
82 ms
tmapctrl.png
79 ms
cb_scout5.png
162 ms
tmapctrl4.png
80 ms
imgs8.png
83 ms
vt
79 ms
vt
78 ms
vt
55 ms
vt
44 ms
vt
41 ms
vt
58 ms
vt
68 ms
vt
60 ms
vt
124 ms
vt
76 ms
vt
126 ms
vt
121 ms
vt
112 ms
vt
90 ms
vt
88 ms
vt
107 ms
vt
173 ms
vt
170 ms
vt
176 ms
vt
157 ms
vt
173 ms
geoflags.de SEO score
![]()
DE
![]()
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geoflags.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 Geoflags.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.
geoflags.de
Open Graph description is not detected on the main page of Geoflags. 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: