6 sec in total
325 ms
5.3 sec
376 ms
Click here to check amazing Preem content for Sweden. Otherwise, check out these important facts you probably never knew about preem.se
Med moderna raffinaderier och drygt 520 tankställen är vår vision att leda omvandlingen mot ett hållbart samhälle.
Visit preem.seWe analyzed Preem.se page load time and found that the first response time was 325 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
preem.se performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value12.0 s
0/100
25%
Value6.8 s
35/100
10%
Value550 ms
54/100
30%
Value0.024
100/100
15%
Value11.4 s
19/100
10%
325 ms
350 ms
62 ms
284 ms
334 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 41% of them (26 requests) were addressed to the original Preem.se, 8% (5 requests) were made to Maps.googleapis.com and 8% (5 requests) were made to Ssl.webserviceaward.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Preem.se.
Page size can be reduced by 1.6 MB (28%)
5.6 MB
4.1 MB
In fact, the total size of Preem.se main page is 5.6 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. Images take 4.7 MB which makes up the majority of the site volume.
Potential reduce by 55.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. This page needs HTML code to be minified as it can gain 8.9 kB, which is 13% 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 55.5 kB or 80% of the original size.
Potential reduce by 973.3 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, Preem needs image optimization as it can save up to 973.3 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 476.7 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 476.7 kB or 70% of the original size.
Potential reduce by 49.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. Preem.se needs all CSS files to be minified and compressed as it can save up to 49.4 kB or 39% of the original size.
Number of requests can be reduced by 26 (48%)
54
28
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Preem. 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 4 to 1 for CSS and as a result speed up the page load time.
preem.se
325 ms
350 ms
jquery.min.js
62 ms
fonts.css
284 ms
application
334 ms
WebResource.axd
231 ms
jsapi
38 ms
head
327 ms
jquery.min.js
33 ms
js
42 ms
application2.js
518 ms
wscSelVisit902401.shtml
695 ms
ECBB610591E9C4E75.css
967 ms
analytics.js
134 ms
logotype.png
126 ms
mastercard-bildspel-bakgrund.jpg
388 ms
mastercard-bildspel.png
2927 ms
lastpall.png
838 ms
litenkarta.png
598 ms
65 ms
preem-dingbats.woff
351 ms
AbJE0FH
50 ms
LEUvwDpsUFP
53 ms
SyFPHvHy4IRELdzP4hNxRzS7GjmIVQ7dFPBgP6vICXS14pYMxd8iONxxQ3gws7OBkoUseL1tnfJSlQMXP82Tx5CHqYzPj3ge4cnhx1L8BskTQUc=
53 ms
EV+QSfemUHXJ8kcyLZB6RzKlS8qHXY9mL9XEHb9ZvYTadZhN+Z9mFyP+lkKcPeHlwQqIW7kfxkbgjml2NHMQqh24KuLdfVOQEulpxS4bi7xAc7rkhPJjZ2UDJQha83rZOeanKgYtP8vQh5HEq49Mjnkd4evyxFL8A6bFBTw==
53 ms
collect
86 ms
puff_site.png
1128 ms
_41a0781.jpg
470 ms
_41a1468.jpg
470 ms
_69p0512.jpg
591 ms
_41a0516.jpg
591 ms
saifa-foretagskort-alla-2015.jpg
599 ms
lastbil-pa-vag.jpg
737 ms
preem-saljare.jpg
724 ms
ui+en.css
79 ms
format+en,default+en,ui+en,corechart+en.I.js
84 ms
collect
155 ms
bakgrund-for-bild-till-hoger.jpg
628 ms
hero_banner_1640x650.png
3203 ms
hero.jpg
853 ms
kaffe.jpg
886 ms
webtrends.min.js
662 ms
ENWNC-UESS8-P6KHH-HLG9G-LBYA8
49 ms
wscSelVisit.css
261 ms
close.gif
354 ms
preem_logga.jpg
356 ms
wsa_logo.png
369 ms
common.js
41 ms
util.js
59 ms
controls.js
57 ms
places_impl.js
41 ms
config.js
161 ms
powered-by-google-on-white3.png
27 ms
autocomplete-icons.png
29 ms
484 ms
hotjar-98135.js
92 ms
modules-1f5c71aea63f8df71401422ed80fbe5f.js
44 ms
visit-data
216 ms
wtid.js
6 ms
233 ms
118 ms
fbevents.js
208 ms
21 ms
preem.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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.
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.
preem.se 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
preem.se SEO score
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
SV
SV
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Preem.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 Preem.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.
preem.se
Open Graph description is not detected on the main page of Preem. 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: