Report Summary

  • 47

    Performance

    Renders faster than
    66% of other websites

  • 48

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

casteland.com

Casteland chateaux medievaux chateaux de la Renaissance castle chateau fort

Page Load Speed

1.7 sec in total

First Response

308 ms

Resources Loaded

1.2 sec

Page Rendered

198 ms

casteland.com screenshot

About Website

Welcome to casteland.com homepage info - get ready to check Casteland best content for France right away, or after learning these important things about casteland.com

les chateaux renaissance, chateaux forts et chateaux de la loire francais du Xe au XVIIIe siecles en images et textes relatif aux seigneurs batisseurs

Visit casteland.com

Key Findings

We analyzed Casteland.com page load time and found that the first response time was 308 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

casteland.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value3.8 s

84/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

casteland.com

308 ms

Stylee3.css

84 ms

menu_dyn.js

161 ms

show_ads.js

6 ms

ephem.js

231 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 50% of them (25 requests) were addressed to the original Casteland.com, 12% (6 requests) were made to France-pittoresque.com and 10% (5 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (534 ms) belongs to the original domain Casteland.com.

Page Optimization Overview & Recommendations

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

Content Size

160.4 kB

After Optimization

111.0 kB

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

HTML Optimization

-76%

Potential reduce by 19.4 kB

  • Original 25.4 kB
  • After minification 23.5 kB
  • After compression 6.0 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 19.4 kB or 76% of the original size.

Image Optimization

-16%

Potential reduce by 15.3 kB

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

JavaScript Optimization

-38%

Potential reduce by 14.6 kB

  • Original 38.2 kB
  • After minification 37.7 kB
  • After compression 23.6 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 14.6 kB or 38% of the original size.

CSS Optimization

-63%

Potential reduce by 163 B

  • Original 258 B
  • After minification 202 B
  • After compression 95 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. Casteland.com needs all CSS files to be minified and compressed as it can save up to 163 B or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (45%)

Requests Now

49

After Optimization

27

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

Accessibility Review

casteland.com accessibility score

48

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

casteland.com best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

casteland.com SEO score

67

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Casteland.com can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Casteland.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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