Report Summary

  • 54

    Performance

    Renders faster than
    72% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

spunky.fr

spunky.fr

Page Load Speed

2.5 sec in total

First Response

359 ms

Resources Loaded

1.9 sec

Page Rendered

206 ms

spunky.fr screenshot

About Website

Welcome to spunky.fr homepage info - get ready to check Spunky best content right away, or after learning these important things about spunky.fr

Visit spunky.fr

Key Findings

We analyzed Spunky.fr page load time and found that the first response time was 359 ms and then it took 2.1 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

spunky.fr performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

35/100

25%

SI (Speed Index)

Value4.8 s

67/100

10%

TBT (Total Blocking Time)

Value420 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.193

64/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

spunky.fr

359 ms

www.anniluce.fr

708 ms

Untitled1.css

240 ms

index.css

239 ms

img0001.png

237 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 8% of them (1 request) were addressed to the original Spunky.fr, 92% (11 requests) were made to Anniluce.fr. The less responsive or slowest element that took the longest time to load (815 ms) relates to the external source Anniluce.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 67.5 kB (22%)

Content Size

313.6 kB

After Optimization

246.1 kB

In fact, the total size of Spunky.fr main page is 313.6 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. Only 10% of websites need less resources to load. Images take 310.8 kB which makes up the majority of the site volume.

HTML Optimization

-64%

Potential reduce by 1.3 kB

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 726 B

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 1.3 kB or 64% of the original size.

Image Optimization

-21%

Potential reduce by 65.7 kB

  • Original 310.8 kB
  • After minification 245.1 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, Spunky needs image optimization as it can save up to 65.7 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-68%

Potential reduce by 518 B

  • Original 766 B
  • After minification 553 B
  • After compression 248 B

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. Spunky.fr needs all CSS files to be minified and compressed as it can save up to 518 B or 68% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

9

After Optimization

9

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

Accessibility Review

spunky.fr accessibility score

53

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

<frame> or <iframe> elements do not have a title

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

spunky.fr 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

SEO Factors

spunky.fr SEO score

83

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Spunky.fr can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Spunky.fr 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 Spunky. 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: