10.9 sec in total
2 sec
7.9 sec
986 ms
Visit fla.de now to see the best up-to-date FLA content for Denmark and also check out these interesting facts you probably never knew about fla.de
Læs de seneste nyheder fra det danske mindretal i Sydslesvig og det grænsenære Sønderjylland.
Visit fla.deWe analyzed Fla.de page load time and found that the first response time was 2 sec and then it took 8.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fla.de performance score
name
value
score
weighting
Value2.8 s
57/100
10%
Value9.1 s
1/100
25%
Value5.1 s
62/100
10%
Value620 ms
48/100
30%
Value0.6
11/100
15%
Value6.5 s
58/100
10%
1977 ms
106 ms
208 ms
212 ms
208 ms
Our browser made a total of 203 requests to load all elements on the main page. We found that 44% of them (89 requests) were addressed to the original Fla.de, 6% (12 requests) were made to Static.xx.fbcdn.net and 5% (11 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Fla.de.
Page size can be reduced by 857.6 kB (39%)
2.2 MB
1.4 MB
In fact, the total size of Fla.de main page is 2.2 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 54.7 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 54.7 kB or 80% of the original size.
Potential reduce by 19.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. FLA images are well optimized though.
Potential reduce by 702.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 702.8 kB or 66% of the original size.
Potential reduce by 80.3 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. Fla.de needs all CSS files to be minified and compressed as it can save up to 80.3 kB or 78% of the original size.
Number of requests can be reduced by 115 (59%)
195
80
The browser has sent 195 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FLA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 62 to 1 for JavaScripts and from 25 to 1 for CSS and as a result speed up the page load time.
www.fla.de
1977 ms
styles.css
106 ms
runya_hhs.css
208 ms
jplayer.blue.monday.css
212 ms
kdl.css
208 ms
typa.css
208 ms
jquery.fancybox-1.3.4.css
212 ms
ticker.css
210 ms
jquery-ui-1.8.21.custom.css
310 ms
css
82 ms
css
93 ms
fn.css
310 ms
comments.css
309 ms
layout_neu_all.css
314 ms
layout_neu.css
311 ms
layout_iso.css
312 ms
bdt.js
408 ms
jquery-1.7.1.min.js
623 ms
jquery-ui-1.8.18.custom.min.js
646 ms
jquery.easing.1.3.js
412 ms
jquery.mousewheel-3.0.4.pack.js
413 ms
jquery.hoverIntent.minified.js
417 ms
jquery.fancybox-1.3.4.js
513 ms
jquery.vticker.js
515 ms
typa.js
514 ms
ticker.js
519 ms
swfobject.js
82 ms
jquery.jplayer.min.js
638 ms
json2.js
615 ms
jquery.infinitescroll.js
717 ms
web.js
628 ms
fx.js
714 ms
kdl.js
714 ms
cookieconsent.min.js
31 ms
adsbygoogle.js
31 ms
show_ads.js
44 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
33 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
39 ms
dc.js
62 ms
small.jpg
1417 ms
banner_fl-arena-1045.png
635 ms
da_flag.gif
171 ms
de_flag.gif
170 ms
Flensborg-Avis-logo-website.png
170 ms
hovermarker.png
169 ms
currentmarker.png
171 ms
pict.php
758 ms
pict.php
388 ms
pict.php
573 ms
pict.php
1023 ms
pict.php
757 ms
pict.php
1022 ms
pict.php
1235 ms
pict.php
1684 ms
pict.php
1590 ms
pict.php
1205 ms
pict.php
1589 ms
pict.php
1714 ms
pict.php
1888 ms
pict.php
2110 ms
pict.php
1892 ms
pict.php
3037 ms
pict.php
2208 ms
pict.php
1988 ms
pict.php
2535 ms
pict.php
2430 ms
pict.php
2700 ms
pict.php
2910 ms
pict.php
2868 ms
pict.php
3159 ms
pict.php
2773 ms
pict.php
3720 ms
pict.php
3256 ms
pict.php
3381 ms
pict.php
3480 ms
sdk.js
47 ms
pict.php
3592 ms
kH7K4InNTm7mmOXXjrA5v_gg4qM5Rpmu0ASAribBgqE.ttf
23 ms
pR0sBQVcY0JZc_ciXjFsKwAUTJOA6-irsSazDq377BE.ttf
25 ms
ca-pub-7972028129903186.js
35 ms
zrt_lookup.html
120 ms
show_ads_impl.js
132 ms
__utm.gif
126 ms
167 ms
SydslesvigTube_icon.png
3104 ms
facebook_icon.jpg
3202 ms
button_zejt-ung.png
3208 ms
banner-flarena.png
3513 ms
flensborg-avis-offset.jpg
3516 ms
xd_arbiter.php
93 ms
xd_arbiter.php
114 ms
ads
154 ms
osd.js
27 ms
ads
304 ms
show_ads_impl.js
244 ms
piwik.js
3107 ms
css
15 ms
m_js_controller.js
20 ms
abg.js
31 ms
googlelogo_color_112x36dp.png
31 ms
nessie_icon_thin_arrow_big_white.png
25 ms
s
15 ms
x_button_blue2.png
7 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
9 ms
ads
223 ms
251 ms
bsredirect5.js
69 ms
ca
29 ms
moatad.js
250 ms
louiseskoekken.png
3119 ms
logo_rsh_fla2014b.png
2967 ms
bst2tv3.html
131 ms
verifyc.js
103 ms
banner_sandpapir.png
2946 ms
sydslesvigudvalget.png
2955 ms
111 ms
adj
105 ms
beacon
86 ms
psa
90 ms
126 ms
0
145 ms
pixel
183 ms
lidar.js
17 ms
sbhK2lTE.js
9 ms
cTrvNaRi.html
23 ms
9dc3ef2caa2d1fde4b5b45c50237f34a.jpg
120 ms
dvbs_src.js
83 ms
verify_selector.js
225 ms
blank.gif
229 ms
bapi
190 ms
Citoyen-Logo_rb.jpg
2765 ms
Flensborg-Avis-logo-mini.png
2771 ms
pixel
14 ms
pixel
19 ms
setuid
123 ms
verify.js
55 ms
sqr8.png
2596 ms
sd
6 ms
icon_yt.png
2723 ms
click%253Fd%253DAPEucNXjgBFt4diq5JMYRPnFuyCGZN4DURmVcXaMCoxN-lc1_YI9mSGIW10VzAVZM_tl2M3n_aUln50q8otDeCEe6r8ZVJUHAA%2526r1%253D;ord=1458271783;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=
122 ms
verifyr.js
37 ms
beacon.js
95 ms
dbapi
68 ms
0
57 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
82 ms
dvtp_src.js
41 ms
durly.js
93 ms
dt
206 ms
dvtp_src_internal26.js
51 ms
dt
207 ms
OptiFree_160x600.html
165 ms
ba.js
132 ms
4.gif
161 ms
t2tv7.html
151 ms
visit.js
85 ms
mere9.gif
2227 ms
52158.js
25 ms
jplayer.blue.monday.jpg
2362 ms
copy.png
11 ms
water.jpg
16 ms
packs.jpg
16 ms
legal.gif
17 ms
avs5639.js
12 ms
event.gif
53 ms
event.jpg
46 ms
box_19_top-right.png
28 ms
ci.png
21 ms
cap
32 ms
ca
4 ms
ca
6 ms
activeview
15 ms
get
6 ms
get
4 ms
activeview
14 ms
activeview
36 ms
piwik.php
496 ms
page.php
295 ms
4n08FrZmW0I.css
22 ms
gPLjjXw4kx2.css
28 ms
q68gy-v_YMF.js
30 ms
YvxwM8R7ol8.js
60 ms
ihptErjAmMX.js
59 ms
10527903_726015254140015_3113054942028091175_n.png
84 ms
12227156_961059513967392_213987461512163711_n.jpg
85 ms
1620941_745440405474099_1830656473_n.jpg
85 ms
988557_571855246289000_2222710784141030136_n.jpg
88 ms
1930489_119232788471922_894216080655727972_n.jpg
116 ms
ZS8q378OQsF.png
69 ms
wL6VQj7Ab77.png
69 ms
s7jcwEQH7Sx.png
68 ms
R9a_DtVRZgv.js
4 ms
cUDgRFxaoIk.js
6 ms
0JBr1QHp8Gi.js
4 ms
kDOzhTr2W91.js
5 ms
layout_neu_max1279.css
105 ms
layout_iso_max1279.css
105 ms
layout_neu_max992.css
106 ms
layout_iso_max992.css
105 ms
layout_neu_max480.css
105 ms
layout_iso_max480.css
106 ms
light-top.css
4 ms
ui
38 ms
logo.png
6 ms
fla.de accessibility score
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 input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes are not valid or misspelled
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
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
fla.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
fla.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
DA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fla.de can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fla.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.
fla.de
Open Graph description is not detected on the main page of FLA. 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: