4.8 sec in total
348 ms
4 sec
406 ms
Welcome to richardbrand.de homepage info - get ready to check Richard Brand best content right away, or after learning these important things about richardbrand.de
Professional experience, contact details, portfolio, etc.: Find out more or get in touch with Richard A. Brand on XING.
Visit richardbrand.deWe analyzed Richardbrand.de page load time and found that the first response time was 348 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
richardbrand.de performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value14.0 s
0/100
25%
Value11.5 s
5/100
10%
Value290 ms
79/100
30%
Value0
100/100
15%
Value8.0 s
43/100
10%
348 ms
2624 ms
105 ms
206 ms
409 ms
Our browser made a total of 37 requests to load all elements on the main page. We found that all of those requests were addressed to Richardbrand.de and no external sources were called. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Richardbrand.de.
Page size can be reduced by 140.9 kB (20%)
697.6 kB
556.7 kB
In fact, the total size of Richardbrand.de main page is 697.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. 25% of websites need less resources to load. Images take 408.7 kB which makes up the majority of the site volume.
Potential reduce by 111.8 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 111.8 kB or 82% of the original size.
Potential reduce by 2.5 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. Richard Brand images are well optimized though.
Potential reduce by 14.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 14.9 kB or 14% of the original size.
Potential reduce by 11.7 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. Richardbrand.de needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 24% of the original size.
Number of requests can be reduced by 22 (63%)
35
13
The browser has sent 35 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Richard Brand. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
richardbrand.de
348 ms
richardbrand.de
2624 ms
main.min.css
105 ms
astra-local-fonts.css
206 ms
style.min.css
409 ms
style.css
306 ms
cookieblocker.min.css
308 ms
spectra-block-positioning.min.css
310 ms
slick.min.css
307 ms
uag-css-429.css
310 ms
jquery.min.js
511 ms
jquery-migrate.min.js
413 ms
custom.js
412 ms
frontend.min.js
413 ms
wp-polyfill-inert.min.js
414 ms
regenerator-runtime.min.js
551 ms
wp-polyfill.min.js
615 ms
dom-ready.min.js
552 ms
main.js
553 ms
spectra-block-positioning.min.js
552 ms
testimonial.min.js
612 ms
imagesloaded.min.js
613 ms
slick.min.js
618 ms
uag-js-429.js
620 ms
tracker.js
621 ms
complianz.min.js
715 ms
cropped-logo_small_icon_only_inverted-45x45.png
191 ms
freizeit-querformat-original-1024x1024.jpeg
492 ms
gcmod-819x1024.jpeg
496 ms
DSC09626-819x1024.jpeg
296 ms
foto-rosa-150x150.jpg
299 ms
fischer-homepage-150x150.jpg
293 ms
Foto-Jan-Daniel-150x150.png
294 ms
logo-4.svg
397 ms
logo-5.svg
399 ms
logo-3.svg
400 ms
logo-1.svg
401 ms
richardbrand.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
richardbrand.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
richardbrand.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
Document uses legible font sizes
EN
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Richardbrand.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Richardbrand.de 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.
richardbrand.de
Open Graph description is not detected on the main page of Richard Brand. 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: