8.6 sec in total
800 ms
7.5 sec
336 ms
Click here to check amazing Lfub content. Otherwise, check out these important facts you probably never knew about lfub.dk
Om Fertilitet | Fertilitet & Tab er en patientforening, som støtter dig før, under og efter fertilitetsbehandling.
Visit lfub.dkWe analyzed Lfub.dk page load time and found that the first response time was 800 ms and then it took 7.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
lfub.dk performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value12.1 s
0/100
25%
Value14.3 s
1/100
10%
Value3,020 ms
2/100
30%
Value0.828
4/100
15%
Value13.9 s
10/100
10%
800 ms
231 ms
312 ms
304 ms
362 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 90% of them (89 requests) were addressed to the original Lfub.dk, 7% (7 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Lfub.dk.
Page size can be reduced by 1.7 MB (71%)
2.3 MB
675.1 kB
In fact, the total size of Lfub.dk main page is 2.3 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. 65% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.
Potential reduce by 37.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. 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 37.4 kB or 79% of the original size.
Potential reduce by 69.6 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. Obviously, Lfub needs image optimization as it can save up to 69.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 720.2 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 720.2 kB or 72% of the original size.
Potential reduce by 841.7 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. Lfub.dk needs all CSS files to be minified and compressed as it can save up to 841.7 kB or 86% of the original size.
Number of requests can be reduced by 74 (82%)
90
16
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lfub. 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 20 to 1 for CSS and as a result speed up the page load time.
www.lfub.dk
800 ms
css
231 ms
css
312 ms
bbpress.css
304 ms
styles.css
362 ms
style.css
411 ms
bootstrap-responsive.css
371 ms
mediaelementplayer.css
479 ms
jquery.fancybox.css
411 ms
hoverex-all.css
475 ms
vector-icons.css
506 ms
jquery.easy-pie-chart.css
518 ms
idangerous.swiper.css
538 ms
frontend.min.css
942 ms
last_minute_fixes.css
547 ms
www.lfub.dk
639 ms
jquery.js
881 ms
jquery-migrate.min.js
639 ms
wp-fade-in-text-news.js
834 ms
picturefill.min.js
857 ms
jquery.easy-pie-chart.js
880 ms
jquery.appear-1.1.1.modified.js
879 ms
modernizr.custom.66803.js
975 ms
animations.js
975 ms
jquery.countdown.min.js
978 ms
waypoints.min.js
979 ms
idangerous.swiper-2.0.min.js
1487 ms
bootstrap.min.js
1487 ms
bootstrap-select.js
1488 ms
core.min.js
1105 ms
widget.min.js
1110 ms
accordion.min.js
3173 ms
mouse.min.js
1208 ms
slider.min.js
1478 ms
resizable.min.js
1482 ms
draggable.min.js
1482 ms
button.min.js
1541 ms
position.min.js
1541 ms
dialog.min.js
1474 ms
tabs.min.js
1255 ms
sortable.min.js
1197 ms
droppable.min.js
1296 ms
style.css
1383 ms
datepicker.min.js
1273 ms
menu.min.js
1204 ms
autocomplete.min.js
1205 ms
frontend.min.js
1551 ms
editor.js
1296 ms
jquery.form.min.js
1286 ms
scripts.js
1263 ms
bootstrap.min.js
1264 ms
jquery.easing.1.1.js
1496 ms
jquery.easing.1.3.js
1478 ms
jquery.mobilemenu.js
1121 ms
isotope.js
1127 ms
jquery.cycle.all.js
1439 ms
customSelect.jquery.min.js
2143 ms
jquery.flexslider-min.js
1357 ms
jquery.fancybox.js
2141 ms
jquery.fancybox-media.js
2138 ms
jquery.carouFredSel-6.1.0-packed.js
2137 ms
mediaelement-and-player.min.js
2064 ms
tooltip.js
2059 ms
jquery.hoverex.js
1959 ms
jquery.imagesloaded.min.js
1688 ms
switcher.js
1684 ms
menu.js
1859 ms
main.js
1863 ms
comment-reply.min.js
1861 ms
jquery.placeholder.min.js
1860 ms
jquery.livequery.js
1803 ms
wp-embed.min.js
1802 ms
wp-emoji-release.min.js
1907 ms
bootstrap.css
2058 ms
flexslider.css
1755 ms
eldo.css
1749 ms
switcher.css
1753 ms
patteren9.jpg
331 ms
page_header.jpg
296 ms
logo.png
241 ms
Banner-cryos.png
242 ms
Banner-ciconia.gif
241 ms
Banner-Ferring.jpg
640 ms
AagaardAnim2.gif
538 ms
bg.jpg
246 ms
banner1.jpg
323 ms
banner2.jpg
322 ms
banner3.jpg
421 ms
banner4.jpg
385 ms
icon_top.png
422 ms
footer_arrow.png
424 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
171 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
170 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
172 ms
dazS1PrQQuCxC3iOAJFEJTqR_3kx9_hJXbbyU8S6IN0.woff
171 ms
y7lebkjgREBJK96VQi37ZobN6UDyHWBl620a-IRfuBk.woff
170 ms
dazS1PrQQuCxC3iOAJFEJR_xHqYgAV9Bl_ZQbYUxnQU.woff
169 ms
7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff
170 ms
moon.svg
1757 ms
lfub.dk 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.
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
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.
lfub.dk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
lfub.dk 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
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lfub.dk can be misinterpreted by Google and other search engines. Our service has detected that Danish is used on the page, and it matches the claimed language. Our system also found out that Lfub.dk 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.
lfub.dk
Open Graph description is not detected on the main page of Lfub. 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: