Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 89% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

docs.graphly.io

Help Docs | Graphly

Page Load Speed

1 sec in total

First Response

337 ms

Resources Loaded

525 ms

Page Rendered

185 ms

docs.graphly.io screenshot

About Website

Welcome to docs.graphly.io homepage info - get ready to check Docs Graphly best content for United States right away, or after learning these important things about docs.graphly.io

FAQs and Support Documentation for Graphly Users

Visit docs.graphly.io

Key Findings

We analyzed Docs.graphly.io page load time and found that the first response time was 337 ms and then it took 710 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

docs.graphly.io performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

33/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

63/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value820 ms

35/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

docs.graphly.io

337 ms

launch-1456833535338.css

18 ms

jquery.min.js

30 ms

app3.min.js

28 ms

graphly-logo-helpdesk.png

112 ms

Our browser made a total of 7 requests to load all elements on the main page. We found that 14% of them (1 request) were addressed to the original Docs.graphly.io, 29% (2 requests) were made to D25gbwvd82b2e5.cloudfront.net and 14% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (337 ms) belongs to the original domain Docs.graphly.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 13.8 kB (4%)

Content Size

344.1 kB

After Optimization

330.3 kB

In fact, the total size of Docs.graphly.io main page is 344.1 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. 15% of websites need less resources to load. Images take 295.2 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 11.8 kB

  • Original 15.4 kB
  • After minification 11.6 kB
  • After compression 3.6 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 3.8 kB, which is 25% 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 11.8 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 2.0 kB

  • Original 295.2 kB
  • After minification 293.3 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. Docs Graphly images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 0 B

  • Original 33.4 kB
  • After minification 33.4 kB
  • After compression 33.4 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.

Requests Breakdown

We found no issues to fix!

Requests Now

5

After Optimization

5

The browser has sent 5 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Docs Graphly. According to our analytics all requests are already optimized.

Accessibility Review

docs.graphly.io accessibility score

96

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

Links do not have a discernible name

Best Practices

docs.graphly.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

docs.graphly.io 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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docs.graphly.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Docs.graphly.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 description is not detected on the main page of Docs Graphly. 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: