Tools & Wizards About Us
castorus.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

castorus.com

Historique, Suivi et analyse d'annonces immobilières : Castorus

Page Load Speed

2.3 sec in total

First Response

194 ms

Resources Loaded

1.8 sec

Page Rendered

334 ms

castorus.com screenshot

About Website

Visit castorus.com now to see the best up-to-date Castorus content for France and also check out these interesting facts you probably never knew about castorus.com

Historique et Suivi d'annonces immobili�res : Castorus

Visit castorus.com

Key Findings

We analyzed Castorus.com page load time and found that the first response time was 194 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 45% of websites can load faster.

Performance Metrics

castorus.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value3,830 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

castorus.com

194 ms

castorus.com

594 ms

font.min.css

239 ms

k.min.css

248 ms

style.master.min.css

266 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 85% of them (35 requests) were addressed to the original Castorus.com, 5% (2 requests) were made to Pagead2.googlesyndication.com and 2% (1 request) were made to Cache.consentframework.com. The less responsive or slowest element that took the longest time to load (760 ms) relates to the external source Iskcommunication.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 162.4 kB (25%)

Content Size

662.1 kB

After Optimization

499.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Castorus.com main page is 662.1 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. 25% of websites need less resources to load. Javascripts take 381.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 146.1 kB

  • Original 189.6 kB
  • After minification 183.4 kB
  • After compression 43.5 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 146.1 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 871 B

  • Original 71.1 kB
  • After minification 70.2 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. Castorus images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 10.0 kB

  • Original 381.8 kB
  • After minification 381.8 kB
  • After compression 371.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. This website has mostly compressed JavaScripts.

CSS Optimization

-28%

Potential reduce by 5.5 kB

  • Original 19.5 kB
  • After minification 14.5 kB
  • After compression 14.1 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. Castorus.com needs all CSS files to be minified and compressed as it can save up to 5.5 kB or 28% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

castorus.com

castorus.com

194 ms

castorus.com

castorus.com

594 ms

font.min.css

font.min.css

239 ms

k.min.css

k.min.css

248 ms

style.master.min.css

style.master.min.css

266 ms

tk.php

tk.php

269 ms

stub

stub

53 ms

cmp

cmp

206 ms

table.min.css

table.min.css

302 ms

jquery-3.6.3.min.js

jquery-3.6.3.min.js

240 ms

scripts.masters.min.js

scripts.masters.min.js

237 ms

js

js

75 ms

jquery.easy-autocomplete.min.js

jquery.easy-autocomplete.min.js

238 ms

home.min.js

home.min.js

238 ms

easy-autocomplete.themes.css

easy-autocomplete.themes.css

238 ms

fglm.js

fglm.js

239 ms

lsid.min.js

lsid.min.js

239 ms

adsbygoogle.js

adsbygoogle.js

236 ms

bg-overlay.svg

bg-overlay.svg

87 ms

logo.png

logo.png

175 ms

extension180.jpg

extension180.jpg

163 ms

3.png

3.png

164 ms

11.png

11.png

163 ms

27.png

27.png

164 ms

16.png

16.png

173 ms

7.png

7.png

175 ms

12.png

12.png

191 ms

1.png

1.png

194 ms

23.png

23.png

224 ms

chrome2023.png

chrome2023.png

251 ms

firefox2023.png

firefox2023.png

248 ms

matomo.js

matomo.js

760 ms

poppins-v6-latin-regular.woff

poppins-v6-latin-regular.woff

169 ms

poppins-v6-latin-700.woff

poppins-v6-latin-700.woff

193 ms

Flaticon2.woff

Flaticon2.woff

206 ms

poppins-v6-latin-italic.woff

poppins-v6-latin-italic.woff

228 ms

poppins-v6-latin-700italic.woff

poppins-v6-latin-700italic.woff

250 ms

Flaticon.woff

Flaticon.woff

262 ms

show_ads_impl.js

show_ads_impl.js

322 ms

Flaticon2.ttf

Flaticon2.ttf

86 ms

Flaticon2.svg

Flaticon2.svg

86 ms

Accessibility Review

castorus.com accessibility score

100

Accessibility Issues

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

castorus.com SEO score

99

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

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Castorus.com 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 Castorus.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

castorus.com

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