Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gravual.com

Gravual - Grafisch Ontwerp Studio in Antwerpen

Page Load Speed

6 sec in total

First Response

1 sec

Resources Loaded

4.2 sec

Page Rendered

830 ms

gravual.com screenshot

About Website

Click here to check amazing Gravual content for United States. Otherwise, check out these important facts you probably never knew about gravual.com

Zorgvuldig uitgewerkte branding, tijdloos grafisch ontwerp en doordacht webdesign.

Visit gravual.com

Key Findings

We analyzed Gravual.com page load time and found that the first response time was 1 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

gravual.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.636

9/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

1018 ms

wp-emoji-release.min.js

169 ms

rgs.css

163 ms

font-awesome.min.css

164 ms

style.css

330 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 84% of them (48 requests) were addressed to the original Gravual.com, 11% (6 requests) were made to Use.typekit.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Gravual.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.0 MB (58%)

Content Size

3.4 MB

After Optimization

1.4 MB

In fact, the total size of Gravual.com main page is 3.4 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. 60% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 161.7 kB

  • Original 183.1 kB
  • After minification 176.5 kB
  • After compression 21.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. 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 161.7 kB or 88% of the original size.

Image Optimization

-16%

Potential reduce by 197.8 kB

  • Original 1.2 MB
  • After minification 1.0 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, Gravual needs image optimization as it can save up to 197.8 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

-78%

Potential reduce by 1.0 MB

  • Original 1.3 MB
  • After minification 1.1 MB
  • After compression 299.6 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 1.0 MB or 78% of the original size.

CSS Optimization

-87%

Potential reduce by 574.7 kB

  • Original 662.9 kB
  • After minification 576.6 kB
  • After compression 88.2 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. Gravual.com needs all CSS files to be minified and compressed as it can save up to 574.7 kB or 87% of the original size.

Requests Breakdown

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

Requests Now

50

After Optimization

27

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

Accessibility Review

gravual.com accessibility score

67

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

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

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

gravual.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

gravual.com SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    NL

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gravual.com can be misinterpreted by Google and other search engines. Our service has detected that Dutch is used on the page, and it does not match the claimed English language. Our system also found out that Gravual.com 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 Gravual. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: