Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

spiga.ch

Spiga.ch - Photographies naturalistes du canton de Neuchâtel (CH)

Page Load Speed

8.9 sec in total

First Response

1.8 sec

Resources Loaded

6.7 sec

Page Rendered

517 ms

spiga.ch screenshot

About Website

Visit spiga.ch now to see the best up-to-date Spiga content and also check out these interesting facts you probably never knew about spiga.ch

Carnets de terrain et portfolios de photographies naturalistes et animalières réalisées au Val-de-Travers et environs par Fabian Spigariol

Visit spiga.ch

Key Findings

We analyzed Spiga.ch page load time and found that the first response time was 1.8 sec and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

spiga.ch performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value34.7 s

0/100

25%

SI (Speed Index)

Value57.2 s

0/100

10%

TBT (Total Blocking Time)

Value33,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.022

100/100

15%

TTI (Time to Interactive)

Value57.6 s

0/100

10%

Network Requests Diagram

www.spiga.ch

1752 ms

wp-emoji-release.min.js

280 ms

styles.css

189 ms

settings.css

283 ms

reset.css

189 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 77% of them (68 requests) were addressed to the original Spiga.ch, 11% (10 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Spiga.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 957.8 kB (31%)

Content Size

3.1 MB

After Optimization

2.1 MB

In fact, the total size of Spiga.ch main page is 3.1 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 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 39.9 kB

  • Original 48.1 kB
  • After minification 46.1 kB
  • After compression 8.2 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 83% of the original size.

Image Optimization

-3%

Potential reduce by 49.4 kB

  • Original 1.9 MB
  • After minification 1.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. Spiga images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 406.4 kB

  • Original 604.4 kB
  • After minification 579.2 kB
  • After compression 198.0 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 406.4 kB or 67% of the original size.

CSS Optimization

-85%

Potential reduce by 462.1 kB

  • Original 546.4 kB
  • After minification 471.8 kB
  • After compression 84.3 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. Spiga.ch needs all CSS files to be minified and compressed as it can save up to 462.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (84%)

Requests Now

77

After Optimization

12

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

Accessibility Review

spiga.ch accessibility score

86

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

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

spiga.ch 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

spiga.ch SEO score

91

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

High

Tap targets are not sized appropriately

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 Spiga.ch 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 Spiga.ch 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 Spiga. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: