Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

foam.se

Teckna försäkring - Jämför och hitta en billig försäkring online

Page Load Speed

1.2 sec in total

First Response

318 ms

Resources Loaded

746 ms

Page Rendered

163 ms

foam.se screenshot

About Website

Welcome to foam.se homepage info - get ready to check Foam best content right away, or after learning these important things about foam.se

Här får du hjälp att hitta en bra och billig försäkring. Vi jämför olika försäkringar och berättar vad du ska tänka på när du ska teckna en ny försäkring.

Visit foam.se

Key Findings

We analyzed Foam.se page load time and found that the first response time was 318 ms and then it took 909 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

foam.se performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

68/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.7 s

91/100

10%

Network Requests Diagram

foam.se

318 ms

style.css

108 ms

t

367 ms

modernaforsakringar.gif

217 ms

star.gif

212 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 77% of them (17 requests) were addressed to the original Foam.se, 9% (2 requests) were made to Track.adtraction.com and 5% (1 request) were made to Adtraction.com. The less responsive or slowest element that took the longest time to load (420 ms) belongs to the original domain Foam.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.3 kB (19%)

Content Size

70.2 kB

After Optimization

57.0 kB

In fact, the total size of Foam.se main page is 70.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. Only 10% of websites need less resources to load. Images take 39.1 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 9.0 kB

  • Original 13.1 kB
  • After minification 12.5 kB
  • After compression 4.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. 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 9.0 kB or 69% of the original size.

Image Optimization

-2%

Potential reduce by 605 B

  • Original 39.1 kB
  • After minification 38.5 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. Foam images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 1.5 kB

  • Original 15.1 kB
  • After minification 15.1 kB
  • After compression 13.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. This website has mostly compressed JavaScripts.

CSS Optimization

-73%

Potential reduce by 2.1 kB

  • Original 2.9 kB
  • After minification 2.4 kB
  • After compression 795 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. Foam.se needs all CSS files to be minified and compressed as it can save up to 2.1 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foam. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.

Accessibility Review

foam.se accessibility score

100

Accessibility Issues

Best Practices

foam.se best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

foam.se SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foam.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and it does not match the claimed English language. Our system also found out that Foam.se 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Foam. 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: