3.6 sec in total
358 ms
2.9 sec
382 ms
Click here to check amazing Flag content. Otherwise, check out these important facts you probably never knew about flag.de
BEST – Ihr Experte für bedruckte Stoffe seit 1921. Fahnendruck für Firmen, Vereine, Kirchen & den Privatgebrauch. ✓Nationalflaggen ✓Organisationsfahnen ✓Rollups ✓Kirchenfahnen ✓Tischfähnchen ✓Werbeban...
Visit flag.deWe analyzed Flag.de page load time and found that the first response time was 358 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
flag.de performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value16.8 s
0/100
25%
Value10.8 s
6/100
10%
Value1,940 ms
8/100
30%
Value0.51
15/100
15%
Value16.0 s
6/100
10%
358 ms
462 ms
109 ms
214 ms
215 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 57% of them (63 requests) were addressed to the original Flag.de, 23% (26 requests) were made to Static.xx.fbcdn.net and 6% (7 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Flag.de.
Page size can be reduced by 700.8 kB (25%)
2.8 MB
2.1 MB
In fact, the total size of Flag.de main page is 2.8 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. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 28.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. 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 28.0 kB or 81% of the original size.
Potential reduce by 48.9 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. Flag images are well optimized though.
Potential reduce by 391.8 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 391.8 kB or 66% of the original size.
Potential reduce by 232.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. Flag.de needs all CSS files to be minified and compressed as it can save up to 232.2 kB or 83% of the original size.
Number of requests can be reduced by 53 (50%)
107
54
The browser has sent 107 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Flag. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
flag.de
358 ms
www.flag.de
462 ms
style.css
109 ms
style.css
214 ms
stylesheet_e582c080b8.css
215 ms
styles.css
229 ms
jquery-1.8.2.min.js
339 ms
jquery-1.7.2.min.js
328 ms
jquery.nivoslider-2.7.1.min.js
215 ms
jquery.ez-bg-resize.js
318 ms
script.js
320 ms
javascript_0b12553063.js
324 ms
slightbox.css
330 ms
prototype.1.7.0.yui.js
530 ms
scriptaculous.js
424 ms
lightbox.2.0.5.yui.js
426 ms
jsfunc.validateform.js
439 ms
bg_top.gif
219 ms
effects.js
126 ms
builder.js
116 ms
RTEmagicC_eb3865f049.png.png
137 ms
logo.png
136 ms
search_b.png
145 ms
main_photo.jpg
455 ms
startseite_fussball_wm.jpg
466 ms
ostern_2013.jpg
693 ms
fruehling3_bluete_2013.jpg
694 ms
slider_bg.png
246 ms
b863a6948e.jpg
367 ms
pic.gif
367 ms
8b13af23d8.jpg
554 ms
2a8451481f.jpg
549 ms
71ba0c4e50.jpg
692 ms
00fb27d4cc.jpg
691 ms
109b5b237e.jpg
692 ms
cdcfde3e4a.jpg
693 ms
2588de5e55.jpg
701 ms
a3ccc4f7b1.jpg
701 ms
757e912c22.jpg
700 ms
674d30b074.jpg
700 ms
94d3c843ed.jpg
701 ms
f2b90d3c06.jpg
720 ms
000d881c2b.jpg
815 ms
693f656549.jpg
813 ms
50c01e0076.jpg
813 ms
a716607b7e.jpg
812 ms
976cd26ef3.jpg
919 ms
c8aa717257.jpg
937 ms
cb19579f14.jpg
913 ms
12265c47da.jpg
913 ms
dcedf30705.jpg
917 ms
e651bdb51b.jpg
917 ms
f508294df5.jpg
1019 ms
c655235b55.jpg
1023 ms
7829cc1cad.jpg
1022 ms
ga.js
60 ms
tZ8m9zgiU6s
124 ms
57c1ce96d7.jpg
950 ms
likebox.php
345 ms
__utm.gif
26 ms
8d27295da3.jpg
901 ms
5bf1b9ce47.jpg
918 ms
null.png
990 ms
www-embed-player-vflfNyN_r.css
68 ms
www-embed-player.js
89 ms
b_button3.png
901 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
53 ms
ad_status.js
42 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
30 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
32 ms
footer_bg.jpg
777 ms
flag_bg.jpg
878 ms
410ucuAGgaJ.css
49 ms
tSbl8xBI27R.css
54 ms
Czh0gDTFcBt.css
61 ms
Ek6lpayKeeB.css
61 ms
EoarYgA68t4.css
72 ms
mxbv-ufzSkZ.css
82 ms
EZGYRcHcChf.css
78 ms
q68gy-v_YMF.js
82 ms
FJmpeSpHpjS.js
81 ms
0wM5s1Khldu.js
116 ms
1bNoFZUdlYZ.js
118 ms
njO1TPvGzoR.js
130 ms
1QuX41zDRrx.js
131 ms
Oagsvfb4VWi.js
126 ms
LTv6ZK-5zxz.js
138 ms
1FCa-btixu2.js
128 ms
DVtj8v6ogQI.js
124 ms
IjqSyiwKeaX.js
135 ms
n6VgtouijQL.js
135 ms
574877_388339224541779_665682428_n.jpg
122 ms
safe_image.php
213 ms
109 ms
safe_image.php
46 ms
safe_image.php
84 ms
safe_image.php
51 ms
545927_388348741207494_1105787118_n.jpg
46 ms
12670147_1045645628811132_7385067700305364203_n.jpg
57 ms
10152582_10152362343124845_446483887_n.jpg
42 ms
12376605_1015967741778921_5500451655532981645_n.jpg
41 ms
545927_388348741207494_1105787118_n.jpg
48 ms
12119097_983424251699937_5715437892289118211_n.jpg
141 ms
wL6VQj7Ab77.png
33 ms
s7jcwEQH7Sx.png
32 ms
QDwYpIaRyfG.png
33 ms
pimRBh7B6ER.png
31 ms
K00K-UgnsKu.png
30 ms
I6-MnjEovm5.js
5 ms
pQrUxxo5oQp.js
7 ms
loading.gif
117 ms
flag.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
<frame> or <iframe> elements do not have a title
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
flag.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
Page has valid source maps
flag.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
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 Flag.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 Flag.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.
flag.de
Open Graph description is not detected on the main page of Flag. 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: