14.9 sec in total
863 ms
8.9 sec
5.1 sec
Visit biggy.de now to see the best up-to-date Biggy content for Germany and also check out these interesting facts you probably never knew about biggy.de
Dank eines Forums, einer Zitate-Datenbank und eines E-Card-Services wird ihr das hoffentlich auch in den nächsten 15 Jahre gelingen.
Visit biggy.deWe analyzed Biggy.de page load time and found that the first response time was 863 ms and then it took 14 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
biggy.de performance score
name
value
score
weighting
Value3.0 s
50/100
10%
Value3.0 s
78/100
25%
Value5.1 s
62/100
10%
Value50 ms
100/100
30%
Value0.053
98/100
15%
Value3.1 s
95/100
10%
863 ms
260 ms
602 ms
600 ms
506 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 81% of them (26 requests) were addressed to the original Biggy.de, 13% (4 requests) were made to S7.addthis.com and 3% (1 request) were made to M.addthisedge.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Biggy.de.
Page size can be reduced by 427.7 kB (63%)
682.3 kB
254.6 kB
In fact, the total size of Biggy.de main page is 682.3 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. 45% of websites need less resources to load. Javascripts take 524.4 kB which makes up the majority of the site volume.
Potential reduce by 29.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 29.0 kB or 74% of the original size.
Potential reduce by 10.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. Obviously, Biggy needs image optimization as it can save up to 10.2 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 352.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 352.9 kB or 67% of the original size.
Potential reduce by 35.6 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. Biggy.de needs all CSS files to be minified and compressed as it can save up to 35.6 kB or 84% of the original size.
Number of requests can be reduced by 17 (55%)
31
14
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Biggy. 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.
www.biggy.de
863 ms
style.css
260 ms
jquery.js
602 ms
jquery-migrate.min.js
600 ms
script.js
506 ms
AJS.js
600 ms
AJS_fx.js
588 ms
gb_scripts.js
1332 ms
gb_styles.css
1410 ms
addthis_widget.js
344 ms
signatur.gif
4045 ms
nav.png
1092 ms
menuitem.png
1091 ms
spacer.gif
1040 ms
subitem.png
1039 ms
header.jpg
1038 ms
header-object.png
1041 ms
post_v.png
1040 ms
post_c.png
1040 ms
postmetadataheader_bg.png
1039 ms
vmenublockheader.png
3909 ms
vmenuitem.png
3856 ms
blockheader.png
3570 ms
_ate.track.config_resp
205 ms
300lo.json
193 ms
client.de.min.json
147 ms
indicator.gif
1047 ms
g_close.gif
333 ms
w_close.gif
333 ms
header_bg.gif
332 ms
sh.886bb8b2fb82aeab6a228151.html
901 ms
counter.750d31a9c5cb74697448.js
562 ms
biggy.de accessibility score
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
Document doesn't have a <title> element
Image elements do not have [alt] attributes
biggy.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
biggy.de SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
N/A
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Biggy.de can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Biggy.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.
biggy.de
Open Graph description is not detected on the main page of Biggy. 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: