Tools & Wizards About Us
foi.se screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

foi.se

Totalförsvarets forskningsinstitut - FOI

Page Load Speed

3.3 sec in total

First Response

554 ms

Resources Loaded

2.6 sec

Page Rendered

222 ms

foi.se screenshot

About Website

Visit foi.se now to see the best up-to-date FOI content for Sweden and also check out these interesting facts you probably never knew about foi.se

FOI:s kärnverksamhet är forskning, metod- och teknikutveckling samt analyser och studier. Myndigheten är uppdragsfinansierad och ligger under Försvarsdepartementet.

Visit foi.se

Key Findings

We analyzed Foi.se page load time and found that the first response time was 554 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

foi.se performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

61/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.692

7/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

foi.se

554 ms

sitevision-responsive-grids.css

175 ms

sitevision-spacing.css

285 ms

SiteVision.css

351 ms

SiteVision.css

446 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 98% of them (49 requests) were addressed to the original Foi.se, 2% (1 request) were made to Stat-ext.foi.se. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Foi.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.4 kB (18%)

Content Size

1.1 MB

After Optimization

868.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Foi.se main page is 1.1 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. 40% of websites need less resources to load. Javascripts take 517.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 75.6 kB

  • Original 91.3 kB
  • After minification 85.9 kB
  • After compression 15.7 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 75.6 kB or 83% of the original size.

Image Optimization

-34%

Potential reduce by 117.3 kB

  • Original 343.8 kB
  • After minification 226.6 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, FOI needs image optimization as it can save up to 117.3 kB or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 347 B

  • Original 517.0 kB
  • After minification 517.0 kB
  • After compression 516.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

-0%

Potential reduce by 202 B

  • Original 109.8 kB
  • After minification 109.8 kB
  • After compression 109.6 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. Foi.se has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 37 (86%)

Requests Now

43

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

foi.se

foi.se

554 ms

sitevision-responsive-grids.css

sitevision-responsive-grids.css

175 ms

sitevision-spacing.css

sitevision-spacing.css

285 ms

SiteVision.css

SiteVision.css

351 ms

SiteVision.css

SiteVision.css

446 ms

portlets.css

portlets.css

452 ms

envision.css

envision.css

464 ms

sv-template-asset.css

sv-template-asset.css

582 ms

webapp-assets.css

webapp-assets.css

497 ms

webapp-assets.css

webapp-assets.css

496 ms

webapp-assets.css

webapp-assets.css

558 ms

sv-template-asset.js

sv-template-asset.js

831 ms

index.js

index.js

574 ms

index.js

index.js

613 ms

index.js

index.js

1069 ms

index.js

index.js

674 ms

webapp-assets.js

webapp-assets.js

682 ms

index.js

index.js

689 ms

jquery.js

jquery.js

879 ms

utils.js

utils.js

790 ms

portlets.js

portlets.js

796 ms

envision.js

envision.js

801 ms

react_17_0.js

react_17_0.js

909 ms

webapp-assets.js

webapp-assets.js

906 ms

webapp-assets.js

webapp-assets.js

910 ms

webapp-assets.js

webapp-assets.js

941 ms

webapp-assets.js

webapp-assets.js

951 ms

webapp-assets.js

webapp-assets.js

1014 ms

webapp-assets.js

webapp-assets.js

1021 ms

webapp-assets.js

webapp-assets.js

1016 ms

webapp_sdk-min.js

webapp_sdk-min.js

1055 ms

matomo.php

matomo.php

817 ms

foi_logo_svg.svg

foi_logo_svg.svg

232 ms

(2)%20shutterstock_1840455238.jpg

(2)%20shutterstock_1840455238.jpg

260 ms

calendar.svg

calendar.svg

260 ms

clock.svg

clock.svg

267 ms

location-dot.svg

location-dot.svg

304 ms

icon-facebook.svg

icon-facebook.svg

312 ms

x-twitter.svg

x-twitter.svg

313 ms

icon-linkedin.svg

icon-linkedin.svg

369 ms

icon-youtube.svg

icon-youtube.svg

367 ms

externallinknewwindow.png

externallinknewwindow.png

379 ms

opensans-regular-webfont.ttf

opensans-regular-webfont.ttf

409 ms

opensans-light-webfont.ttf

opensans-light-webfont.ttf

425 ms

opensans-bold-webfont.ttf

opensans-bold-webfont.ttf

425 ms

fa-light-300.woff

fa-light-300.woff

675 ms

fa-regular-400.woff

fa-regular-400.woff

569 ms

fa-solid-900.woff

fa-solid-900.woff

588 ms

dots-pattern-flipped.png

dots-pattern-flipped.png

625 ms

chevron-right.svg

chevron-right.svg

302 ms

Accessibility Review

foi.se accessibility score

93

Accessibility Issues

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

Best Practices

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

High

Page has valid source maps

SEO Factors

foi.se SEO score

98

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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

foi.se

Open Graph data is detected on the main page of FOI. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: