Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 55

    SEO

    Google-friendlier than
    20% of websites

Page Load Speed

1.9 sec in total

First Response

338 ms

Resources Loaded

1.5 sec

Page Rendered

77 ms

fortime.se screenshot

About Website

Click here to check amazing Fortime content for Sweden. Otherwise, check out these important facts you probably never knew about fortime.se

Visit fortime.se

Key Findings

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

Performance Metrics

fortime.se performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.2 s

20/100

10%

Network Requests Diagram

fortime.se

338 ms

calendar.css

96 ms

style.css

279 ms

jquery-ui-1.7.2.custom.css

282 ms

bootstrap-glyphicons.css

9 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 96% of them (25 requests) were addressed to the original Fortime.se, 4% (1 request) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Fortime.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 828.8 kB (83%)

Content Size

997.7 kB

After Optimization

168.9 kB

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

HTML Optimization

-75%

Potential reduce by 2.4 kB

  • Original 3.1 kB
  • After minification 2.7 kB
  • After compression 779 B

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 414 B, 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 2.4 kB or 75% of the original size.

JavaScript Optimization

-83%

Potential reduce by 670.0 kB

  • Original 804.4 kB
  • After minification 495.1 kB
  • After compression 134.4 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 670.0 kB or 83% of the original size.

CSS Optimization

-82%

Potential reduce by 156.5 kB

  • Original 190.1 kB
  • After minification 178.2 kB
  • After compression 33.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. Fortime.se needs all CSS files to be minified and compressed as it can save up to 156.5 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (92%)

Requests Now

25

After Optimization

2

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

Accessibility Review

fortime.se accessibility score

68

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

fortime.se best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

fortime.se SEO score

55

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

Document doesn't have a <title> element

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fortime.se can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Fortime.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 Fortime. 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: