Analyze

typo3.net: Deutschsprachiges Forum zu TYPO3 CMS | typo3.net

TYPO3.net - Die große TYPO3-Community von Mittwald CM Service. FAQ, Tutorials und ein starkes Forum helfen bei allen Fragen rund um TYPO3 CMS.

Page load speed analysis

  • 66/100

    Normal result
  • 6

    Successful tests
  • 2

    Failed tests
  • First response

    314 ms

  • Resources loaded

    5.5 sec

  • Page rendered

    202 ms

  • Total page load time

    6 sec

Welcome to typo3.net homepage info - get ready to check TYPO3 best content for Germany right away, or after learning these important things about typo3.net

We analyzed Typo3.net page load time and found that the first response time was 314 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Page optimization

  • HTML 39.8 kB
    Images 497.3 kB
    Javascripts 148.7 kB
    CSS 0 B

    In fact, the total size of Typo3.net main page is 685.8 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. 20% of websites need less resources to load. Images take 497.3 kB which makes up the majority of the site volume.

    • Original 39.8 kB
    • After minification 31.0 kB
    • After compression 5.6 kB

    HTML optimization

    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 8.8 kB, which is 22% 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 34.3 kB or 86% of the original size.

    • Original 497.3 kB
    • After optimization 452.2 kB

    Image optimization

    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. TYPO3 images are well optimized though.

    • Original 148.7 kB
    • After minification 148.7 kB
    • After compression 52.5 kB

    JavaScript optimization

    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 96.2 kB or 65% of the original size.

Network requests diagram

  • typo3.net
  • www.typo3.net
  • news-basic.1441314585.css
  • stylesheet_7bf94e70b5.1441314756.css
  • typo3_forum.1441314585.css
  • bootstrap.1441314585.css
  • style.1441314585.css
  • style.1441314585.css
  • jquery-1.11.1.min.1441314585.js
  • jquery.min.js
  • bootstrap.min.1441314585.js
  • jquery.markitup.1441314585.js
  • jquery.socialshareprivacy.min.1441314585.js
  • forum.1441314585.js
  • base.1441314585.js
  • juetland.jpg
  • logo.png
  • iconset.png
  • csm_AvatarEmpty_79f391d428.png
  • typo3-mask.png
  • typo3-cms-74.jpg
  • typo3-extension-web2pdf.jpg
  • hosting-germany-229x265.jpg
  • mittwald_sidebar.png
  • csm_AvatarEmpty_c53ef4fd82.png
  • csm_61_9dtlQn2L._SY355__563aa10626_acf74170a0.jpg
  • csm_51e371da4127b879c9f17_8773369569.jpg
  • moderator.png
  • csm_5135d6ae831fd_87c115933d_110b4692f4.png
  • csm_rainer_karnowski_celmedia_87732d9abf_381329503f.jpg
  • dokumente_downloads.png
  • eStrategy_Banner.png
  • piwik.js
  • index.php
  • share-regular-webfont.woff
  • share-bold-webfont.woff

Our browser made a total of 36 requests to load all elements on the main page. We found that 94% of them (34 requests) were addressed to the original Typo3.net, 3% (1 request) were made to Ajax.googleapis.com and 3% (1 request) were made to Piwik.typo3.net. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Typo3.net.

Additional info on typo3.net

Requests

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

8

Javascripts

17

Images

6

CSS

3

AJAX

34

All

Possible request optimization

1

Javascripts

17

Images

1

CSS

3

AJAX

12

Optimized

22

All

Normal result

Redirects

As for redirects, our browser was forwarded to http://www.typo3.net/ before it reached this domain.

IP address

This IP address is dedicated to Typo3.net. This is the best domain hosting practice .

Normal result

IP Trace

typo3.net

37.202.5.183

DNS records

Type Host Target/ip TTL Other
A

typo3.net

37.202.5.183 21599
NS

typo3.net

ns2.typo3server.com 21599
NS

typo3.net

ns3.dnsmittwald.de 21599
NS

typo3.net

dns.typo3server.com 21599
SOA

typo3.net

21599 Mname: dns.typo3server.com
Rname: support.mittwald.de
Serial: 1707270001
Refresh: 28800
Retry: 7200
Expire: 604800
Minimum-ttl: 3600

Language and encoding

Good result

Language

DE de language flag

Detected

DE de language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Typo3.net 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 Typo3.net 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.

HTTPS certificate

SSL Certificate

Typo3.net has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Poor result

Visitor World Map

Country of origin for 80.7% of all visits is Germany. It’s good for Typo3.net that their server is also located in Germany, as that enables the majority of their visitors to benefit from a much faster page load time.

Good result

Poor result

Social Sharing Optimization

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

typo3.net

Share this report in social media

Analyze another website

Analyze