Tools & Wizards About Us
720.fi screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

720.fi

Kotisivu - 720 Degrees

Page Load Speed

2.4 sec in total

First Response

233 ms

Resources Loaded

1.5 sec

Page Rendered

644 ms

720.fi screenshot

About Website

Click here to check amazing 720 content for Finland. Otherwise, check out these important facts you probably never knew about 720.fi

Tee laadukkaasta sisäympäristöstä kilpailuetusi ja käytä samalla 50% vähemmän työaikaa sisäympäristöhaasteisiin

Visit 720.fi

Key Findings

We analyzed 720.fi page load time and found that the first response time was 233 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

720.fi performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value760 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

Network Requests Diagram

720.fi

233 ms

720.io

210 ms

style.min.css

31 ms

classic-themes.min.css

72 ms

app.css

35 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original 720.fi, 67% (31 requests) were made to 720.io and 11% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (261 ms) relates to the external source 720.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 47.9 kB (2%)

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 720.fi main page is 2.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.0 kB

  • Original 49.3 kB
  • After minification 47.0 kB
  • After compression 10.3 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 39.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 6.3 kB

  • Original 1.7 MB
  • After minification 1.7 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. 720 images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.6 kB

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

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 59.7 kB
  • After minification 59.7 kB
  • After compression 59.7 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. 720.fi has all CSS files already compressed.

Requests Breakdown

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

Requests Now

42

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 720. 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 10 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

720.fi

720.fi

233 ms

720.io

720.io

210 ms

style.min.css

style.min.css

31 ms

classic-themes.min.css

classic-themes.min.css

72 ms

app.css

app.css

35 ms

jquery.min.js

jquery.min.js

45 ms

jquery-migrate.min.js

jquery-migrate.min.js

45 ms

main.js

main.js

51 ms

gds.esm.js

gds.esm.js

65 ms

033b65fee9.js

033b65fee9.js

53 ms

slick.min.js

slick.min.js

27 ms

app.js

app.js

54 ms

ZkhUCT4FmGQ

ZkhUCT4FmGQ

96 ms

pale-circle.svg

pale-circle.svg

30 ms

frontpage-hero-scaled.jpg

frontpage-hero-scaled.jpg

36 ms

white-circle.svg

white-circle.svg

33 ms

720-infografiikka-1.jpg

720-infografiikka-1.jpg

31 ms

720-infografiikka-2.jpg

720-infografiikka-2.jpg

36 ms

720-infografiikka-3.jpg

720-infografiikka-3.jpg

52 ms

720-infografiikka-4.jpg

720-infografiikka-4.jpg

68 ms

susanna-vilen.png

susanna-vilen.png

53 ms

hemso-1.png

hemso-1.png

57 ms

seb-1.png

seb-1.png

68 ms

eq.png

eq.png

63 ms

cbre.png

cbre.png

79 ms

are.png

are.png

77 ms

sponda.png

sponda.png

113 ms

logo.svg

logo.svg

91 ms

swegon-logotype-pos-rgb.svg

swegon-logotype-pos-rgb.svg

114 ms

www-player.css

www-player.css

8 ms

www-embed-player.js

www-embed-player.js

31 ms

base.js

base.js

100 ms

blockstyles.css

blockstyles.css

261 ms

ad_status.js

ad_status.js

236 ms

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

jZnaD5i84OOj95f_CaIDPNlD8clIrXO563EFyn6Jvvo.js

172 ms

embed.js

embed.js

48 ms

blockstyles.css

blockstyles.css

69 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

70 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

73 ms

id

id

40 ms

cookieconsent.min.css

cookieconsent.min.css

134 ms

Create

Create

141 ms

main.css

main.css

124 ms

cookieconsent.min.css

cookieconsent.min.css

121 ms

main.css

main.css

28 ms

GenerateIT

GenerateIT

27 ms

Accessibility Review

720.fi accessibility score

91

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Best Practices

720.fi best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

720.fi SEO score

86

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

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

    FI

  • Language Claimed

    FI

  • Encoding

    UTF-8

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

720.fi

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