Report Summary

  • 38

    Performance

    Renders faster than
    58% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

preem.se

Sveriges största drivmedelsbolag - Preem.se

Page Load Speed

6 sec in total

First Response

325 ms

Resources Loaded

5.3 sec

Page Rendered

376 ms

preem.se screenshot

About Website

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.se

Key Findings

We 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.

Performance Metrics

preem.se performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value550 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

preem.se

325 ms

350 ms

jquery.min.js

62 ms

fonts.css

284 ms

application

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 Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (28%)

Content Size

5.6 MB

After Optimization

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.

HTML Optimization

-80%

Potential reduce by 55.5 kB

  • Original 69.5 kB
  • After minification 60.6 kB
  • After compression 14.0 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.

Image Optimization

-21%

Potential reduce by 973.3 kB

  • Original 4.7 MB
  • After minification 3.8 MB

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.

JavaScript Optimization

-70%

Potential reduce by 476.7 kB

  • Original 685.3 kB
  • After minification 679.8 kB
  • After compression 208.6 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.

CSS Optimization

-39%

Potential reduce by 49.4 kB

  • Original 127.5 kB
  • After minification 124.0 kB
  • After compression 78.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. 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.

Requests Breakdown

Number of requests can be reduced by 26 (48%)

Requests Now

54

After Optimization

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.

Accessibility Review

preem.se accessibility score

70

Accessibility Issues

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

High

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

preem.se best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

preem.se SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    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.

Social Sharing Optimization

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: