5.9 sec in total
379 ms
5.3 sec
269 ms
Welcome to trefor.dk homepage info - get ready to check TREFOR best content for Denmark right away, or after learning these important things about trefor.dk
Vi gør os hver dag umage for at sikre høj forsyningssikkerhed og stabilitet i elnettet og i vand- og varmeforsyningen. Læs mere her »
Visit trefor.dkWe analyzed Trefor.dk page load time and found that the first response time was 379 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
trefor.dk performance score
name
value
score
weighting
Value3.9 s
24/100
10%
Value5.9 s
14/100
25%
Value7.7 s
24/100
10%
Value210 ms
88/100
30%
Value0.023
100/100
15%
Value13.0 s
13/100
10%
379 ms
602 ms
187 ms
260 ms
43 ms
Our browser made a total of 173 requests to load all elements on the main page. We found that 89% of them (154 requests) were addressed to the original Trefor.dk, 2% (4 requests) were made to Use.typekit.net and 1% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Trefor.dk.
Page size can be reduced by 3.9 MB (33%)
11.9 MB
8.0 MB
In fact, the total size of Trefor.dk main page is 11.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. Images take 7.3 MB which makes up the majority of the site volume.
Potential reduce by 31.8 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. This page needs HTML code to be minified as it can gain 4.8 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 31.8 kB or 75% of the original size.
Potential reduce by 167.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. TREFOR images are well optimized though.
Potential reduce by 3.3 MB
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 3.3 MB or 81% of the original size.
Potential reduce by 383.4 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. Trefor.dk needs all CSS files to be minified and compressed as it can save up to 383.4 kB or 84% of the original size.
Number of requests can be reduced by 142 (85%)
167
25
The browser has sent 167 CSS, Javascripts, AJAX and image requests in order to completely render the main page of TREFOR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 143 to 1 for JavaScripts and as a result speed up the page load time.
trefor.dk
379 ms
trefor.dk
602 ms
xnc5gjw.js
187 ms
mq.min.css
260 ms
bootstrap-glyphicons.css
43 ms
font-awesome.min.css
43 ms
modernizr.custom.js
366 ms
VisitorIdentification.js
280 ms
WebResource.axd
684 ms
jquery.min.js
47 ms
angular.min.js
51 ms
bootstrap.min.js
42 ms
jquery-ui.min-autocomplete.js
621 ms
jquery.ui.widget.js
488 ms
history.js
355 ms
iframeResizer.js
492 ms
jquery.fileupload.js
490 ms
jquery.iframe-transport.js
490 ms
jquery.matchHeight.js
489 ms
angular-resource.js
604 ms
angular-sanitize.js
592 ms
select.js
678 ms
ui-bootstrap-tpls.js
788 ms
angular-locale_da-dk.js
758 ms
video.js
912 ms
video.novtt.js
887 ms
videojs-ie8.js
793 ms
da.js
786 ms
de.js
793 ms
en.js
871 ms
Youtube.js
872 ms
headroom.js
880 ms
enquire.js
882 ms
d3.js
1779 ms
modernizr.custom.js
1019 ms
grid.js
1019 ms
dawa-autocomplete.js
1021 ms
app.js
1019 ms
JsonWithDateParse.js
1020 ms
stay_standalone.js
1063 ms
login.js
1066 ms
addresslookup.directive.js
1069 ms
addresslookup.controller.js
1079 ms
blockInteraction.directive.js
1091 ms
customFlowValidation.directive.js
894 ms
cvr-lookup.directive.js
896 ms
fiberOrderFlow.controller.js
823 ms
analytics.js
124 ms
gtm.js
180 ms
formatPrice.filter.js
698 ms
d
18 ms
d
25 ms
d
45 ms
orderFlow.directive.js
715 ms
orderFlowStep.directive.js
774 ms
productRequirementFlowValidation.directive.js
779 ms
sameAs.directive.js
778 ms
scroll-animate.directive.js
784 ms
collect
22 ms
collect
44 ms
ewii.js
96 ms
telephonyHelpers.directive.js
699 ms
validateCancelledAlternativepayer.directive.js
748 ms
validateTelephonyGroup.directive.js
740 ms
sp.js
105 ms
preflow.controller.js
637 ms
telephonyOverview.controller.js
612 ms
i
389 ms
signUpForFiber.controller.js
595 ms
matchHeight.js
647 ms
accesslist.controller.js
657 ms
accountinfo.controller.js
651 ms
loginRemove.directive.js
655 ms
address.service.js
599 ms
callme.controller.js
654 ms
callme.directive.js
661 ms
callme.service.js
654 ms
caseOverview.controller.js
657 ms
iframe_api
41 ms
chart.directive.js
548 ms
normscale.directive.js
625 ms
normscale.service.js
632 ms
acceptCustomerRelation.controller.js
628 ms
acceptCustomerRelation.service.js
629 ms
acceptCustomerRelationNewCustomer.controller.js
635 ms
www-widgetapi.js
28 ms
acceptCustomerRelationUseExistingCustomer.controller.js
670 ms
editaccess.controller.js
671 ms
grantaccess.controller.js
671 ms
customerReferenceSearch.directive.js
662 ms
dictionary.service.js
649 ms
productSelection.directive.js
677 ms
productSelector.directive.js
670 ms
form.controller.js
665 ms
form.directive.js
659 ms
formgroup.directive.js
643 ms
formgroupValidation.directive.js
612 ms
formInputValidation.directive.js
672 ms
formsubmit.directive.js
665 ms
installationCtrl.js
652 ms
installationServ.js
582 ms
annualreport.controller.js
605 ms
annualreport.service.js
673 ms
invoice.service.js
660 ms
invoiceoverview.controller.js
651 ms
modal.directive.js
597 ms
modal.service.js
585 ms
staticmodal.controller.js
601 ms
notification.controller.js
662 ms
notification.service.js
656 ms
productCtrl.js
591 ms
consumptionsummary.controller.js
583 ms
consumptionsummary.service.js
583 ms
customerrelationRemove.directive.js
597 ms
masterdata.controller.js
636 ms
consumptionalarm.controller.js
571 ms
consumptionalarm.service.js
559 ms
consumptionreport.controller.js
568 ms
consumptionreport.service.js
560 ms
tab.service.js
569 ms
tabnavigation.directive.js
556 ms
address.js
566 ms
autoheight.directive.js
564 ms
checklist.directive.js
566 ms
error.directive.js
561 ms
fileupload.directive.js
504 ms
formSubmitted.directive.js
547 ms
helpText.directive.js
562 ms
htmlPopup.directive.js
563 ms
matchheight.directive.js
563 ms
nemid.directive.js
565 ms
ngminmax.directive.js
537 ms
popup.directive.js
548 ms
sameAs.directive.js
561 ms
spinner.directive.js
572 ms
trim.filter.js
556 ms
trust.filter.js
554 ms
googleanalytics.service.js
543 ms
widget.service.js
548 ms
wizard.directive.js
574 ms
wizard.controller.js
552 ms
moveExistingForm.directive.js
567 ms
hero.js
563 ms
href.js
541 ms
iframe.js
544 ms
matchHeight.js
592 ms
megamenu.js
596 ms
scrollbelow.js
591 ms
scrolltop.js
586 ms
videojs.js
573 ms
wffm.js
545 ms
burgermenu.js
590 ms
tooltip.js
588 ms
main.min.js
635 ms
bg-grid.png
594 ms
sprit-sheet.png
854 ms
top-shadow.png
553 ms
sub-overlay.png
652 ms
TREFORVandogVarmelogo_neg_ny_web_RGB.png
652 ms
overlay-left.png
649 ms
overlay-right.png
650 ms
trefor_varme_mor_og_dreng_ved_radiator.jpg
655 ms
box-bg.png
598 ms
612327TREFOR-vandhane.jpg
1915 ms
foto-til-web-612x306.jpg
639 ms
612x327_DrengPaaGulv.jpg
665 ms
612x327_Mobiltelefon-i-haand.jpg
693 ms
ewii_selvbetjening_pc.jpg
698 ms
GetAlertMessage
623 ms
trefor_vand_kvinde_drikker_af_vandhane.jpg
214 ms
p.gif
16 ms
trefor_varme_mor_og_dreng_ved_radiator.jpg
322 ms
trefor_vand_kvinde_drikker_af_vandhane.jpg
854 ms
trefor.dk 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
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
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.
trefor.dk best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
trefor.dk 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
DA
DA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trefor.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 Trefor.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.
trefor.dk
Open Graph data is detected on the main page of TREFOR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: