4.3 sec in total
592 ms
3.6 sec
163 ms
Click here to check amazing Forge TYPO3 content for Germany. Otherwise, check out these important facts you probably never knew about forge.typo3.org
Redmine
Visit forge.typo3.orgWe analyzed Forge.typo3.org page load time and found that the first response time was 592 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
forge.typo3.org performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value2.5 s
89/100
25%
Value3.6 s
87/100
10%
Value190 ms
91/100
30%
Value0
100/100
15%
Value2.9 s
96/100
10%
592 ms
498 ms
152 ms
554 ms
422 ms
Our browser made a total of 48 requests to load all elements on the main page. We found that 71% of them (34 requests) were addressed to the original Forge.typo3.org, 25% (12 requests) were made to Typo3.org and 4% (2 requests) were made to Piwik.typo3.org. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Forge.typo3.org.
Page size can be reduced by 939.9 kB (79%)
1.2 MB
244.8 kB
In fact, the total size of Forge.typo3.org main page is 1.2 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. 25% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 12.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. This page needs HTML code to be minified as it can gain 2.1 kB, which is 12% 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 12.5 kB or 75% of the original size.
Potential reduce by 3.4 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, Forge TYPO3 needs image optimization as it can save up to 3.4 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 878.7 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 878.7 kB or 81% of the original size.
Potential reduce by 45.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. Forge.typo3.org needs all CSS files to be minified and compressed as it can save up to 45.4 kB or 80% of the original size.
Number of requests can be reduced by 31 (69%)
45
14
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Forge 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 24 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
forge.typo3.org
592 ms
forge.typo3.org
498 ms
application.css
152 ms
prototype.js
554 ms
effects.js
422 ms
dragdrop.js
433 ms
controls.js
442 ms
application.js
348 ms
custom-scripts.js
353 ms
jquery.jqplot.min.css
444 ms
jquery-1.6.2.min.js
772 ms
jquery-ui-1.8.16.custom.min.js
882 ms
jquery.jeditable.mini.js
614 ms
jquery.scrollfollow.js
631 ms
jquery.jqplot.js
1067 ms
jqplot.highlighter.js
661 ms
jqplot.canvasTextRenderer.min.js
706 ms
jqplot.canvasAxisTickRenderer.min.js
725 ms
jqplot.enhancedLegendRenderer.min.js
756 ms
jquery.cookie.js
799 ms
server_variables.js
1217 ms
common.js
850 ms
burndown.js
867 ms
jstoolbar.js
892 ms
textile.js
945 ms
jstoolbar-en.js
984 ms
jstoolbar.css
983 ms
sponsors.js
494 ms
application.css
848 ms
background-greygradient.gif
96 ms
a97d655e725b3fce76d07eb77b940ef8-mid.jpg
102 ms
header_bg.png
127 ms
home.png
96 ms
projects.png
120 ms
help.png
127 ms
custom-topheader.jpg
219 ms
e9ba9900bedb31b8155943e5d9f840bf-mid.jpg
205 ms
64a7c7e082b40ff14b20bc724760aefa-mid.jpg
303 ms
a496b48dec55908b82459365575d9b0e-mid.jpg
316 ms
388fffd29fcebc15bcb7709116ce5049-mid.jpg
315 ms
65d86f4bdd4b0947ec808e6f73a490d7-mid.jpg
336 ms
47efdd76e0a4a94b0e4b74d38a0a2810-mid.jpg
337 ms
77a12d780022335572904ebf12d51960-mid.jpg
335 ms
9b87b3ee61a314f2fa5f7a6fa8b8aa47-mid.jpg
395 ms
02002757b95b82bcc76d047ecd8f63b0-mid.jpg
446 ms
tue.png
412 ms
piwik.js
1003 ms
piwik.php
214 ms
forge.typo3.org 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
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.
forge.typo3.org 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
forge.typo3.org 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Forge.typo3.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Forge.typo3.org 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.
forge.typo3.org
Open Graph description is not detected on the main page of Forge 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: