Tools & Wizards About Us
inkloud.es screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    82% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

inkloud.es

INKLOUD 2 SPAIN S.L.U. - Del Fabricante al Mayorista

Page Load Speed

2.6 sec in total

First Response

841 ms

Resources Loaded

1.6 sec

Page Rendered

199 ms

inkloud.es screenshot

About Website

Welcome to inkloud.es homepage info - get ready to check INKLOUD best content for Spain right away, or after learning these important things about inkloud.es

Vendita all'ingrosso. Dalla fabbrica al rivenditore

Visit inkloud.es

Key Findings

We analyzed Inkloud.es page load time and found that the first response time was 841 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 35% of websites can load faster.

Performance Metrics

inkloud.es performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

64/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value3.8 s

85/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.8 s

79/100

10%

Network Requests Diagram

inkloud.es

841 ms

style.css

532 ms

tooltip.css

458 ms

tooltip.js

429 ms

inkloud3.png

581 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 78% of them (36 requests) were addressed to the original Inkloud.es, 9% (4 requests) were made to S3.eu-central-1.amazonaws.com and 4% (2 requests) were made to Superbanner.org. The less responsive or slowest element that took the longest time to load (841 ms) belongs to the original domain Inkloud.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 109.1 kB (37%)

Content Size

298.0 kB

After Optimization

188.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inkloud.es main page is 298.0 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 168.8 kB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 48.9 kB

  • Original 53.8 kB
  • After minification 37.4 kB
  • After compression 4.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. This page needs HTML code to be minified as it can gain 16.4 kB, which is 31% 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 48.9 kB or 91% of the original size.

Image Optimization

-5%

Potential reduce by 9.1 kB

  • Original 168.8 kB
  • After minification 159.7 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. INKLOUD images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 37.2 kB

  • Original 58.9 kB
  • After minification 58.8 kB
  • After compression 21.8 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 37.2 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 13.9 kB

  • Original 16.4 kB
  • After minification 13.4 kB
  • After compression 2.5 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. Inkloud.es needs all CSS files to be minified and compressed as it can save up to 13.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (60%)

Requests Now

45

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inkloud.es

inkloud.es

841 ms

style.css

style.css

532 ms

tooltip.css

tooltip.css

458 ms

tooltip.js

tooltip.js

429 ms

inkloud3.png

inkloud3.png

581 ms

top1_1.jpg

top1_1.jpg

271 ms

top1_2.jpg

top1_2.jpg

272 ms

button_go.jpg

button_go.jpg

356 ms

ESP.gif

ESP.gif

240 ms

ENG.jpg

ENG.jpg

363 ms

CHI.GIF

CHI.GIF

386 ms

ITA.jpg

ITA.jpg

395 ms

POR.gif

POR.gif

450 ms

top4_1.jpg

top4_1.jpg

469 ms

top1_4.jpg

top1_4.jpg

448 ms

ondaVerde.jpg

ondaVerde.jpg

276 ms

Cat_1_c310set.jpg

Cat_1_c310set.jpg

648 ms

Cat_24_INFORMATI.jpg

Cat_24_INFORMATI.jpg

661 ms

Cat_25_LED.jpg

Cat_25_LED.jpg

397 ms

Cat_26_MYPHONE.jpg

Cat_26_MYPHONE.jpg

512 ms

right1_1.jpg

right1_1.jpg

291 ms

right2_1.jpg

right2_1.jpg

354 ms

right2_2.jpg

right2_2.jpg

400 ms

bnr_horizontal_solutiongraphic_335x80.gif

bnr_horizontal_solutiongraphic_335x80.gif

204 ms

right2_but.jpg

right2_but.jpg

402 ms

botton1_1.jpg

botton1_1.jpg

468 ms

botton1_3.jpg

botton1_3.jpg

509 ms

botton1_2.jpg

botton1_2.jpg

508 ms

botton1_4.jpg

botton1_4.jpg

517 ms

work.php

work.php

248 ms

top1_3.jpg

top1_3.jpg

462 ms

top3_1.jpg

top3_1.jpg

505 ms

top3_3.jpg

top3_3.jpg

507 ms

top3_2.jpg

top3_2.jpg

517 ms

top4_2.jpg

top4_2.jpg

526 ms

left2_1.jpg

left2_1.jpg

540 ms

left2_3.jpg

left2_3.jpg

567 ms

left2_2.jpg

left2_2.jpg

613 ms

center2_1.jpg

center2_1.jpg

619 ms

center2_2.jpg

center2_2.jpg

627 ms

center2_4.jpg

center2_4.jpg

634 ms

center2_5.jpg

center2_5.jpg

651 ms

ga.js

ga.js

29 ms

__utm.gif

__utm.gif

12 ms

line.gif

line.gif

73 ms

468_60.gif

468_60.gif

86 ms

Accessibility Review

inkloud.es accessibility score

86

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

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

inkloud.es best practices score

77

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

inkloud.es SEO score

50

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    >

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inkloud.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish 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 Inkloud.es main page’s claimed encoding is >. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

inkloud.es

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