Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 84% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 96

    SEO

    Google-friendlier than
    91% of websites

splio.com

Splio | Plateforme de CRM intelligent

Page Load Speed

3.4 sec in total

First Response

509 ms

Resources Loaded

2.1 sec

Page Rendered

868 ms

splio.com screenshot

About Website

Visit splio.com now to see the best up-to-date Splio content for United States and also check out these interesting facts you probably never knew about splio.com

Plateforme de CRM intelligent pour les retailers : CDP + Activation, Marketing Automation, Predictive AI, Loyalty et Mobile Wallets.

Visit splio.com

Key Findings

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

Performance Metrics

splio.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value19.9 s

0/100

10%

TBT (Total Blocking Time)

Value15,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value25.7 s

0/100

10%

Network Requests Diagram

splio.com

509 ms

language-selector.css

268 ms

font.css

82 ms

jquery2.1.1.min.js

346 ms

style.css

268 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 68% of them (76 requests) were addressed to the original Splio.com, 30% (34 requests) were made to Webdocs.splio.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (841 ms) relates to the external source Webdocs.splio.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 175.4 kB (43%)

Content Size

408.7 kB

After Optimization

233.4 kB

In fact, the total size of Splio.com main page is 408.7 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. 50% of websites need less resources to load. Images take 205.5 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 39.9 kB

  • Original 50.8 kB
  • After minification 50.8 kB
  • After compression 10.8 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 39.9 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 25.5 kB

  • Original 205.5 kB
  • After minification 179.9 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. Obviously, Splio needs image optimization as it can save up to 25.5 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 63.4 kB

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

CSS Optimization

-83%

Potential reduce by 46.5 kB

  • Original 55.7 kB
  • After minification 44.6 kB
  • After compression 9.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. Splio.com needs all CSS files to be minified and compressed as it can save up to 46.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (12%)

Requests Now

106

After Optimization

93

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

Accessibility Review

splio.com accessibility score

94

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

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

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

High

Missing source maps for large first-party JavaScript

SEO Factors

splio.com SEO score

96

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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