Tools & Wizards About Us
rest.li screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    57% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

rest.li

Rest.li - A framework for building RESTful architectures at scale

Page Load Speed

2.3 sec in total

First Response

231 ms

Resources Loaded

1.8 sec

Page Rendered

332 ms

rest.li screenshot

About Website

Welcome to rest.li homepage info - get ready to check Rest best content for United States right away, or after learning these important things about rest.li

A REST framework for building scalable service architectures using dynamic discovery and simple asynchronous APIs

Visit rest.li

Key Findings

We analyzed Rest.li page load time and found that the first response time was 231 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

rest.li performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.6 s

71/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

rest.li

231 ms

76 ms

icon

334 ms

main.css

204 ms

font-awesome.css

334 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 6% of them (1 request) were addressed to the original Rest.li, 69% (11 requests) were made to Linkedin.github.io and 13% (2 requests) were made to Netdna.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (344 ms) relates to the external source Code.jquery.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 6.8 kB (74%)

Content Size

9.2 kB

After Optimization

2.4 kB

  • HTML

In fact, the total size of Rest.li main page is 9.2 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. 40% of websites need less resources to load. HTML takes 9.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 6.8 kB

  • Original 9.2 kB
  • After minification 7.1 kB
  • After compression 2.4 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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 22% 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 6.8 kB or 74% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (50%)

Requests Now

8

After Optimization

4

  • JavaScript
  • CSS

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

Network Requests Diagram

rest.li

rest.li

231 ms

76 ms

icon

icon

334 ms

main.css

main.css

204 ms

font-awesome.css

font-awesome.css

334 ms

jquery-3.0.0.min.js

jquery-3.0.0.min.js

344 ms

search-input.js

search-input.js

255 ms

jquery.min.js

jquery.min.js

294 ms

materialize.min.js

materialize.min.js

318 ms

init.js

init.js

254 ms

Roboto-Regular.woff

Roboto-Regular.woff

54 ms

Roboto-Medium.woff

Roboto-Medium.woff

52 ms

Roboto-Light.woff

Roboto-Light.woff

84 ms

Roboto-Thin.woff

Roboto-Thin.woff

52 ms

Roboto-Bold.woff

Roboto-Bold.woff

77 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

48 ms

Accessibility Review

rest.li accessibility score

78

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

rest.li best practices score

83

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

SEO Factors

rest.li SEO score

92

Search Engine Optimization Advices

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 Rest.li 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 Rest.li 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

rest.li

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