1.6 sec in total
329 ms
1.2 sec
76 ms
Visit perlgeek.de now to see the best up-to-date Perlgeek content for Germany and also check out these interesting facts you probably never knew about perlgeek.de
Visit perlgeek.deWe analyzed Perlgeek.de page load time and found that the first response time was 329 ms and then it took 1.3 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.
perlgeek.de performance score
name
value
score
weighting
Value2.0 s
83/100
10%
Value2.0 s
97/100
25%
Value3.1 s
93/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value2.0 s
99/100
10%
329 ms
407 ms
98 ms
98 ms
197 ms
Our browser made a total of 11 requests to load all elements on the main page. We found that all of those requests were addressed to Perlgeek.de and no external sources were called. The less responsive or slowest element that took the longest time to load (407 ms) belongs to the original domain Perlgeek.de.
Page size can be reduced by 11.7 kB (64%)
18.4 kB
6.7 kB
In fact, the total size of Perlgeek.de main page is 18.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. Only 5% of websites need less resources to load. CSS take 12.0 kB which makes up the majority of the site volume.
Potential reduce by 4.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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 4.3 kB or 68% of the original size.
Potential reduce by 7.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. Perlgeek.de needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 61% of the original size.
Number of requests can be reduced by 8 (89%)
9
1
The browser has sent 9 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Perlgeek. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for CSS and as a result speed up the page load time.
perlgeek.de
329 ms
perlgeek.de
407 ms
layout_2col_left_13.css
98 ms
base.css
98 ms
syntax.css
197 ms
nav_shinybuttons.css
297 ms
basemod.css
294 ms
basemod_2col_left_13.css
295 ms
content.css
295 ms
print_003_draft.css
294 ms
print_base.css
98 ms
perlgeek.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.
perlgeek.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
perlgeek.de SEO score
EN
DE
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Perlgeek.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 Perlgeek.de 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.
perlgeek.de
Open Graph description is not detected on the main page of Perlgeek. 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: