Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

inkblood.net

Inkblood.net | Olivier Giner | Aquarelles, peintures, illustrations, textes

Page Load Speed

6.7 sec in total

First Response

1 sec

Resources Loaded

5.3 sec

Page Rendered

438 ms

inkblood.net screenshot

About Website

Welcome to inkblood.net homepage info - get ready to check Inkblood best content right away, or after learning these important things about inkblood.net

Inkblood.net : Olivier Giner, Auteur-illustrateur aux textes, illustrations, aquarelles, peintures originales, psychédéliques et poétiques

Visit inkblood.net

Key Findings

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

Performance Metrics

inkblood.net performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value13.7 s

1/100

10%

TBT (Total Blocking Time)

Value540 ms

54/100

30%

CLS (Cumulative Layout Shift)

Value0.447

20/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

www.inkblood.net

1025 ms

font-awesome.min.css

21 ms

96 ms

dashicons.min.css

234 ms

242 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 55% of them (36 requests) were addressed to the original Inkblood.net, 8% (5 requests) were made to Img.inkblood.net and 6% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Inkblood.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.5 kB (3%)

Content Size

8.4 MB

After Optimization

8.2 MB

In fact, the total size of Inkblood.net main page is 8.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. Images take 7.9 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 59.5 kB

  • Original 75.4 kB
  • After minification 73.1 kB
  • After compression 15.9 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 59.5 kB or 79% of the original size.

Image Optimization

-1%

Potential reduce by 96.2 kB

  • Original 7.9 MB
  • After minification 7.8 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. Inkblood images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 57.8 kB

  • Original 395.2 kB
  • After minification 395.2 kB
  • After compression 337.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 57.8 kB or 15% of the original size.

CSS Optimization

-0%

Potential reduce by 15 B

  • Original 35.7 kB
  • After minification 35.7 kB
  • After compression 35.7 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. Inkblood.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (36%)

Requests Now

55

After Optimization

35

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

Accessibility Review

inkblood.net accessibility score

97

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.

Best Practices

inkblood.net 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

inkblood.net SEO score

93

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

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

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