4.3 sec in total
201 ms
2.7 sec
1.4 sec
Click here to check amazing Schischa content. Otherwise, check out these important facts you probably never knew about schischa.cc
Ein Blog über allerlei Unnützes, was um mich rum passiert.
Visit schischa.ccWe analyzed Schischa.cc page load time and found that the first response time was 201 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
schischa.cc performance score
name
value
score
weighting
Value2.6 s
62/100
10%
Value3.4 s
67/100
25%
Value4.6 s
70/100
10%
Value80 ms
99/100
30%
Value0
100/100
15%
Value3.9 s
89/100
10%
201 ms
936 ms
95 ms
190 ms
282 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that 60% of them (36 requests) were addressed to the original Schischa.cc, 8% (5 requests) were made to W.soundcloud.com and 8% (5 requests) were made to F.vimeocdn.com. The less responsive or slowest element that took the longest time to load (936 ms) belongs to the original domain Schischa.cc.
Page size can be reduced by 888.8 kB (54%)
1.7 MB
765.0 kB
In fact, the total size of Schischa.cc main page is 1.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 45% of websites need less resources to load. Javascripts take 721.7 kB which makes up the majority of the site volume.
Potential reduce by 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 43.5 kB or 73% of the original size.
Potential reduce by 35.9 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, Schischa needs image optimization as it can save up to 35.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 489.0 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 489.0 kB or 68% of the original size.
Potential reduce by 320.4 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. Schischa.cc needs all CSS files to be minified and compressed as it can save up to 320.4 kB or 57% of the original size.
Number of requests can be reduced by 30 (54%)
56
26
The browser has sent 56 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Schischa. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
schischa.cc
201 ms
schischa.cc
936 ms
wp-emoji-release.min.js
95 ms
settings.css
190 ms
main.min.css
282 ms
css
55 ms
base.css
283 ms
skeleton.css
286 ms
css
66 ms
screen.css
287 ms
style.css
291 ms
jquery.fancybox-1.3.7.min.css
290 ms
jquery.js
468 ms
jquery-migrate.min.js
374 ms
fluidimage.js
376 ms
jquery.themepunch.tools.min.js
495 ms
jquery.themepunch.revolution.min.js
385 ms
plugins-combined.js
386 ms
script.js
493 ms
wp-embed.min.js
491 ms
jquery.fancybox-1.3.7.min.js
514 ms
jquery.easing.pack.js
515 ms
jquery.mousewheel.min.js
612 ms
574 ms
575 ms
103728987
515 ms
dark_mosaic.png
460 ms
logo.png
460 ms
sprites_post_types.png
458 ms
chrome-ohne-device-scale-300x169.png
459 ms
chrome-mit-device-scale-300x169.png
459 ms
sprites_20.png
458 ms
screenshot_2015-04-14-12-09-09-169x300.png
734 ms
screenshot_2015-04-14-12-08-22-169x300.png
707 ms
screenshot_2015-04-14-12-05-44-169x300.png
707 ms
me-again.jpg
873 ms
picons36.png
569 ms
picons39.png
568 ms
picons42.png
708 ms
picons43.png
707 ms
piwik.js
905 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
399 ms
GcIHC9QEwVkrA19LJU1qlC3USBnSvpkopQaUR-2r7iU.ttf
404 ms
count.js
517 ms
88x31.png
63 ms
80x15.png
48 ms
player.js
131 ms
player.css
109 ms
ga.js
24 ms
vuid.min.js
125 ms
__utm.gif
31 ms
interstate-0ab59479718c8235122cad6b16a66953d725c43a.css
268 ms
widget-0511d506.css
74 ms
widget-d9304090.js
157 ms
count-data.js
126 ms
proxy.html
54 ms
486070738.webp
131 ms
1.svg
22 ms
logo-200x120-177df3dd.png
29 ms
print.css
97 ms
schischa.cc 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.
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
<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.
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
Form elements do not have associated labels
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
schischa.cc best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
schischa.cc SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Schischa.cc can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Schischa.cc 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.
schischa.cc
Open Graph data is detected on the main page of Schischa. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: