Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fastory.io

Fastory | Create mobile contests Facebook and Instagram certified

Page Load Speed

7 sec in total

First Response

164 ms

Resources Loaded

5.3 sec

Page Rendered

1.5 sec

fastory.io screenshot

About Website

Visit fastory.io now to see the best up-to-date Fastory content for United States and also check out these interesting facts you probably never knew about fastory.io

Increase your conversions through attractive mobile experiences. Create immersive and impactful marketing campaign for Snapchat, Instagram, Facebook and Twitter with the leading mobile-first marketing...

Visit fastory.io

Key Findings

We analyzed Fastory.io page load time and found that the first response time was 164 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

fastory.io performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value4,160 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.558

13/100

15%

TTI (Time to Interactive)

Value49.1 s

0/100

10%

Network Requests Diagram

www.fastory.io

164 ms

jquery-1.7.1.js

75 ms

LanguageSwitcher.css

90 ms

slick.min-3.css

222 ms

showcase-carousel.min.css

252 ms

Our browser made a total of 198 requests to load all elements on the main page. We found that 52% of them (103 requests) were addressed to the original Fastory.io, 10% (19 requests) were made to Story.tl and 5% (9 requests) were made to No-cache.hubspot.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Story.tl.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.6 MB (23%)

Content Size

7.3 MB

After Optimization

5.7 MB

In fact, the total size of Fastory.io main page is 7.3 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. Only a small number of websites need less resources to load. Images take 6.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 166.9 kB

  • Original 201.1 kB
  • After minification 184.0 kB
  • After compression 34.2 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 166.9 kB or 83% of the original size.

Image Optimization

-16%

Potential reduce by 960.0 kB

  • Original 6.1 MB
  • After minification 5.2 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. Obviously, Fastory needs image optimization as it can save up to 960.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-54%

Potential reduce by 479.5 kB

  • Original 894.0 kB
  • After minification 894.0 kB
  • After compression 414.5 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 479.5 kB or 54% of the original size.

CSS Optimization

-43%

Potential reduce by 39.7 kB

  • Original 92.8 kB
  • After minification 62.6 kB
  • After compression 53.1 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. Fastory.io needs all CSS files to be minified and compressed as it can save up to 39.7 kB or 43% of the original size.

Requests Breakdown

Number of requests can be reduced by 77 (42%)

Requests Now

184

After Optimization

107

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

Accessibility Review

fastory.io accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

Best Practices

fastory.io best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fastory.io SEO score

83

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

Links do not have descriptive text

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

High

Tap targets are not sized appropriately

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 Fastory.io 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 Fastory.io 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 data is detected on the main page of Fastory. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: