3.1 sec in total
405 ms
2.5 sec
156 ms
Welcome to dom.se homepage info - get ready to check Dom best content for Sweden right away, or after learning these important things about dom.se
Visit dom.seWe analyzed Dom.se page load time and found that the first response time was 405 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
dom.se performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value3.8 s
54/100
25%
Value7.8 s
23/100
10%
Value280 ms
81/100
30%
Value0.005
100/100
15%
Value8.0 s
42/100
10%
405 ms
1092 ms
478 ms
243 ms
248 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dom.se, 61% (36 requests) were made to Domstol.se and 19% (11 requests) were made to F1.eu.readspeaker.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Domstol.se.
Page size can be reduced by 418.6 kB (56%)
747.2 kB
328.6 kB
In fact, the total size of Dom.se main page is 747.2 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. 35% of websites need less resources to load. Javascripts take 512.6 kB which makes up the majority of the site volume.
Potential reduce by 30.1 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 8.0 kB, which is 20% 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 30.1 kB or 76% of the original size.
Potential reduce by 900 B
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. Dom images are well optimized though.
Potential reduce by 293.5 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 293.5 kB or 57% of the original size.
Potential reduce by 94.1 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. Dom.se needs all CSS files to be minified and compressed as it can save up to 94.1 kB or 81% of the original size.
Number of requests can be reduced by 41 (72%)
57
16
The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
dom.se
405 ms
www.domstol.se
1092 ms
dvStyles.css
478 ms
dvChrome.css
243 ms
dvNoScript.css
248 ms
dvIllustrationstyle.css
371 ms
NoScript.js
248 ms
ReadSpeaker.js
75 ms
dvScripts.js
358 ms
jquery-ui.js
15 ms
jquery.ui.core.js
278 ms
jquery.ui.widget.js
138 ms
jquery.ui.button.js
277 ms
jquery.ui.position.js
279 ms
jquery.ui.autocomplete.js
280 ms
infoPopups.js
384 ms
element.js
36 ms
domstol.siteseeker.se
411 ms
analytics.js
27 ms
dovbkg.gif
134 ms
spriteIcons.gif
134 ms
searchbutton_inactive.gif
134 ms
sd_color_left.gif
136 ms
old_man.jpg
229 ms
startpageSearchCourtMap.gif
257 ms
rattshjalp_taxor.jpg
365 ms
skilsmassa3a.jpg
367 ms
arbeta_sveriges_domstolar_start6.jpg
371 ms
play_icon.gif
257 ms
rss_icon.gif
362 ms
mail_icon2.gif
362 ms
topfooternav_bkg.gif
361 ms
topnav_bottom.gif
466 ms
factnav_sides.gif
469 ms
subjectnav_bkg.gif
478 ms
bluebox_corners.gif
476 ms
dottedlinewhite.gif
479 ms
greybox_corners.gif
482 ms
dottedlineblack.gif
584 ms
dottedlineblack.gif
586 ms
footernav_top.gif
597 ms
ReadSpeaker.Styles.css
39 ms
ReadSpeaker.Core.js
62 ms
ReadSpeaker.pub.Config.js
90 ms
collect
13 ms
translateelement.css
57 ms
main.js
83 ms
ReadSpeaker.lib.Facade.adapter.jquery.js
30 ms
ReadSpeaker.Common.Settings.js
50 ms
ReadSpeaker.PlayerAPI.js
50 ms
ReadSpeaker.HL.js
49 ms
ReadSpeaker.ui.js
66 ms
element_main.js
41 ms
ReadSpeaker.enlargeHL.js
61 ms
ReadSpeaker.enlargeHL.css
47 ms
translate_24dp.png
36 ms
l
51 ms
googlelogo_color_42x16dp.png
29 ms
dvPrint.css
121 ms
dom.se 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
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.
dom.se 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
dom.se 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
SV
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dom.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it matches the claimed language. Our system also found out that Dom.se 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.
dom.se
Open Graph description is not detected on the main page of Dom. 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: