Report Summary

  • 31

    Performance

    Renders faster than
    52% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 65

    SEO

    Google-friendlier than
    25% of websites

fra.me

FRAME Cloud Platform · Run any software in a browser

Page Load Speed

1.8 sec in total

First Response

60 ms

Resources Loaded

891 ms

Page Rendered

874 ms

fra.me screenshot

About Website

Visit fra.me now to see the best up-to-date Fra content for India and also check out these interesting facts you probably never knew about fra.me

Run any software in a browser. Sign up now!

Visit fra.me

Key Findings

We analyzed Fra.me page load time and found that the first response time was 60 ms and then it took 1.8 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

fra.me performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,550 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

fra.me

60 ms

base.css

23 ms

style.css

109 ms

featherlight.min.css

29 ms

font-awesome.min.css

84 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 63% of them (40 requests) were addressed to the original Fra.me, 6% (4 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Code.createjs.com. The less responsive or slowest element that took the longest time to load (276 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 834.0 kB (14%)

Content Size

6.1 MB

After Optimization

5.3 MB

In fact, the total size of Fra.me main page is 6.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. 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 4.9 MB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 28.0 kB

  • Original 38.1 kB
  • After minification 35.3 kB
  • After compression 10.1 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 28.0 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 36.0 kB

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

JavaScript Optimization

-65%

Potential reduce by 622.7 kB

  • Original 960.9 kB
  • After minification 956.3 kB
  • After compression 338.1 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 622.7 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 147.3 kB

  • Original 177.3 kB
  • After minification 152.8 kB
  • After compression 30.0 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. Fra.me needs all CSS files to be minified and compressed as it can save up to 147.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (46%)

Requests Now

57

After Optimization

31

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

Accessibility Review

fra.me accessibility score

62

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

High

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

High

Image elements do not have [alt] attributes

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

fra.me best practices score

75

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

Browser errors were logged to the console

SEO Factors

fra.me SEO score

65

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Fra.me 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 Fra.me 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 Fra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: