Tools & Wizards About Us
fasty.ovh screenshot

Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

fasty.ovh

Fasty ! A blazing fast CMS built on top of openresty / Lua & arangoDB / Foxx

Page Load Speed

12.5 sec in total

First Response

224 ms

Resources Loaded

11.4 sec

Page Rendered

856 ms

fasty.ovh screenshot

About Website

Visit fasty.ovh now to see the best up-to-date Fasty content and also check out these interesting facts you probably never knew about fasty.ovh

Looking for a blazing fast multi-tenant CMS ? Here you are ! Build an API, define your datatypes, render views from your AQL requests. You can do anything you want. Openresty, Lua, Lapis, Arangodb & R...

Visit fasty.ovh

Key Findings

We analyzed Fasty.ovh page load time and found that the first response time was 224 ms and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

fasty.ovh performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.4 s

91/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value750 ms

39/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

fasty.ovh

224 ms

fasty.ovh

138 ms

all.js

449 ms

bf1lML04d0ofby9PKPyO4vWl4Y0=.js

20 ms

Gpg5yc+UhXfh8h91mrvemBd7gCM=.js

122 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 29% of them (6 requests) were addressed to the original Fasty.ovh, 29% (6 requests) were made to Resize.ovh and 10% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (10.6 sec) relates to the external source Resize.ovh.

Page Optimization Overview & Recommendations

Page size can be reduced by 33.5 kB (6%)

Content Size

518.7 kB

After Optimization

485.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fasty.ovh main page is 518.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 442.6 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 30.2 kB

  • Original 37.5 kB
  • After minification 37.4 kB
  • After compression 7.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 30.2 kB or 80% of the original size.

Image Optimization

-34%

Potential reduce by 3.1 kB

  • Original 9.1 kB
  • After minification 6.0 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, Fasty needs image optimization as it can save up to 3.1 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 220 B

  • Original 442.6 kB
  • After minification 442.6 kB
  • After compression 442.3 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 17 B

  • Original 29.6 kB
  • After minification 29.6 kB
  • After compression 29.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. Fasty.ovh has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 5 (38%)

Requests Now

13

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fasty.ovh

fasty.ovh

224 ms

fasty.ovh

fasty.ovh

138 ms

all.js

all.js

449 ms

bf1lML04d0ofby9PKPyO4vWl4Y0=.js

bf1lML04d0ofby9PKPyO4vWl4Y0=.js

20 ms

Gpg5yc+UhXfh8h91mrvemBd7gCM=.js

Gpg5yc+UhXfh8h91mrvemBd7gCM=.js

122 ms

BDc-SsWjj41hbgy214QlQMRlTKY=.css

BDc-SsWjj41hbgy214QlQMRlTKY=.css

362 ms

-nrqR-1F1sOWiLIhVDyzp8VfwXc=.css

-nrqR-1F1sOWiLIhVDyzp8VfwXc=.css

51 ms

js

js

88 ms

112

112

422 ms

fasty

fasty

254 ms

329851353

329851353

418 ms

made-with-bulma--black.png

made-with-bulma--black.png

206 ms

982c7390-bffa-11e9-b8b8-7dffa8888a54

982c7390-bffa-11e9-b8b8-7dffa8888a54

10629 ms

58dac8d0-48c2-11ea-aae7-a3c70233f1bc

58dac8d0-48c2-11ea-aae7-a3c70233f1bc

10642 ms

c34e0790-d13a-11e9-af35-f3d0dd89f378

c34e0790-d13a-11e9-af35-f3d0dd89f378

10625 ms

ce95e870-d13a-11e9-af35-f3d0dd89f378

ce95e870-d13a-11e9-af35-f3d0dd89f378

10169 ms

d142e000-d13a-11e9-af35-f3d0dd89f378

d142e000-d13a-11e9-af35-f3d0dd89f378

10340 ms

js

js

87 ms

analytics.js

analytics.js

49 ms

collect

collect

41 ms

774765856-ad1d75f0da5c3de36ecf62136d194e95f041ae4acc61566d0fcdc8ff65054649-d

774765856-ad1d75f0da5c3de36ecf62136d194e95f041ae4acc61566d0fcdc8ff65054649-d

458 ms

Accessibility Review

fasty.ovh accessibility score

83

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fasty.ovh 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

SEO Factors

fasty.ovh SEO score

92

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

fasty.ovh

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