Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

wild.cat

wild.cat » Maintenance Mode

Page Load Speed

5.2 sec in total

First Response

2.1 sec

Resources Loaded

2.9 sec

Page Rendered

201 ms

wild.cat screenshot

About Website

Click here to check amazing Wild content. Otherwise, check out these important facts you probably never knew about wild.cat

Disseny web i gràfic ● Web and graphic design ● Diseño web y gráfico

Visit wild.cat

Key Findings

We analyzed Wild.cat page load time and found that the first response time was 2.1 sec and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

wild.cat performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value1.2 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

wild.cat

2068 ms

autoptimize_e90741ae07e0c66120e8b42ab4bd7dc1.css

158 ms

wild.cat

580 ms

css

25 ms

autoptimize_085886096901a5f83fb11837e7a35641.js

324 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 74% of them (17 requests) were addressed to the original Wild.cat, 9% (2 requests) were made to Google-analytics.com and 9% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Wild.cat.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.4 kB (46%)

Content Size

511.4 kB

After Optimization

276.0 kB

In fact, the total size of Wild.cat main page is 511.4 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. 35% of websites need less resources to load. Javascripts take 214.9 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 8.4 kB

  • Original 11.6 kB
  • After minification 11.6 kB
  • After compression 3.3 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 8.4 kB or 72% of the original size.

Image Optimization

-7%

Potential reduce by 12.2 kB

  • Original 187.2 kB
  • After minification 175.0 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. Wild images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 133.0 kB

  • Original 214.9 kB
  • After minification 214.9 kB
  • After compression 81.9 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 133.0 kB or 62% of the original size.

CSS Optimization

-84%

Potential reduce by 81.9 kB

  • Original 97.7 kB
  • After minification 97.6 kB
  • After compression 15.9 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. Wild.cat needs all CSS files to be minified and compressed as it can save up to 81.9 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (15%)

Requests Now

20

After Optimization

17

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

Accessibility Review

wild.cat accessibility score

100

Accessibility Issues

Best Practices

wild.cat best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

wild.cat SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wild.cat can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Wild.cat 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 Wild. 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: