4.4 sec in total
385 ms
3.8 sec
175 ms
Welcome to facilit.com homepage info - get ready to check Facilit best content right away, or after learning these important things about facilit.com
Norges ledende web-baserte system for FDVU. Forvaltning, drift, vedlikehold og utvikling av bygg og anlegg. Modulbasert for ulike fagfelt.
Visit facilit.comWe analyzed Facilit.com page load time and found that the first response time was 385 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
facilit.com performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value16.6 s
0/100
25%
Value12.1 s
4/100
10%
Value3,830 ms
1/100
30%
Value0.156
74/100
15%
Value15.0 s
8/100
10%
385 ms
480 ms
740 ms
222 ms
561 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 96% of them (49 requests) were addressed to the original Facilit.com, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Facilit.com.
Page size can be reduced by 119.0 kB (16%)
766.4 kB
647.3 kB
In fact, the total size of Facilit.com main page is 766.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. 25% of websites need less resources to load. Images take 587.3 kB which makes up the majority of the site volume.
Potential reduce by 13.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 13.5 kB or 73% of the original size.
Potential reduce by 2.4 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. Facilit images are well optimized though.
Potential reduce by 102.3 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 102.3 kB or 64% of the original size.
Potential reduce by 859 B
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. Facilit.com needs all CSS files to be minified and compressed as it can save up to 859 B or 65% of the original size.
Number of requests can be reduced by 20 (41%)
49
29
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Facilit. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
facilit.com
385 ms
www.facilit.com
480 ms
css.php
740 ms
forside.css
222 ms
jquery.1.4.3.js
561 ms
jquery.superfish.js
227 ms
jquery.cycle.js
227 ms
hoverIntent.min.js
332 ms
html5shiv.js
448 ms
matchMedia.js
452 ms
matchMedia.addListener.js
453 ms
iepngfix_tilebg.js
552 ms
jquery.random.js
672 ms
jquery.form.js
788 ms
js.js
679 ms
bg-body.png
112 ms
ga.js
63 ms
bg-ramme.png
340 ms
logo.png
221 ms
threelines.png
226 ms
button-open-login.png
228 ms
bg-login-links.gif
228 ms
icons-login-links.gif
292 ms
bg-nav.png
444 ms
nav-li-hover.png
451 ms
bg-nav-a.png
451 ms
knapp-sok.png
451 ms
bg-header-kol3.gif
515 ms
sitat.png;w;38;h;36
557 ms
Mesta.gif;w;126;h;36
662 ms
rom-eiendom.png;w;116;h;36
676 ms
Venator-logo.jpg;w;80;h;79
676 ms
ntfk-logo.png;w;50;h;54
676 ms
mrfylke-logo.gif;w;50;h;50
735 ms
unn_logo.gif;w;96;h;62
782 ms
arendal-logo.gif;w;38;h;56
888 ms
facilit-fasade.jpg;w;690;h;292
1003 ms
facilit-galleri.jpg;w;690;h;292
1009 ms
alfheim.jpg;w;690;h;292
1120 ms
framsenteret.jpg;w;690;h;292
1178 ms
fylkeshuset.jpg;w;690;h;292
1455 ms
kunstforeningen.jpg;w;690;h;292
1455 ms
nerstranda.jpg;w;690;h;292
1797 ms
tromsoMuseum.jpg;w;690;h;292
1797 ms
bg-jq-boks.png
1880 ms
pin.png
1891 ms
a-pil.png
1992 ms
bg-nyhet.gif
1911 ms
bg-nyhet-h1.png
2082 ms
siteman-cms-dark-70.png
2104 ms
__utm.gif
17 ms
facilit.com 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-*] attributes do not match their roles
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 toggle fields do not have accessible names
[aria-*] attributes do not have valid values
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
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.
facilit.com 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
Page has valid source maps
facilit.com 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
Tap targets are not sized appropriately
NO
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facilit.com can be misinterpreted by Google and other search engines. Our service has detected that Norwegian 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 Facilit.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
facilit.com
Open Graph description is not detected on the main page of Facilit. 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: