Tools & Wizards About Us
typo3.biz screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

typo3.biz

The TYPO3 Project and Community – Open Source CMS

Page Load Speed

2.8 sec in total

First Response

227 ms

Resources Loaded

2.3 sec

Page Rendered

308 ms

typo3.biz screenshot

About Website

Visit typo3.biz now to see the best up-to-date TYPO3 content and also check out these interesting facts you probably never knew about typo3.biz

TYPO3 is a free enterprise-class CMS based on PHP. It combines open source code with reliability and true scalability. This is the official project website.

Visit typo3.biz

Key Findings

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

Performance Metrics

typo3.biz performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

22/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0.011

100/100

15%

TTI (Time to Interactive)

Value11.2 s

19/100

10%

Network Requests Diagram

typo3.biz

227 ms

typo3.org

549 ms

main.min.css

477 ms

styles.css

284 ms

styles.css

285 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Typo3.biz, 64% (43 requests) were made to Typo3.org and 21% (14 requests) were made to My.typo3.org. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source My.typo3.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.0 kB (3%)

Content Size

6.1 MB

After Optimization

5.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Typo3.biz main page is 6.1 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. 55% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 142.7 kB

  • Original 165.7 kB
  • After minification 132.3 kB
  • After compression 23.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. This page needs HTML code to be minified as it can gain 33.4 kB, which is 20% 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 142.7 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 23.3 kB

  • Original 5.8 MB
  • After minification 5.7 MB

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.

JavaScript Optimization

-25%

Potential reduce by 32.0 kB

  • Original 125.6 kB
  • After minification 125.6 kB
  • After compression 93.6 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 32.0 kB or 25% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (28%)

Requests Now

58

After Optimization

42

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 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 13 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

typo3.biz

typo3.biz

227 ms

typo3.org

typo3.org

549 ms

main.min.css

main.min.css

477 ms

styles.css

styles.css

284 ms

styles.css

styles.css

285 ms

typo3_roadmap.css

typo3_roadmap.css

288 ms

news-basic.css

news-basic.css

284 ms

main.min.js

main.min.js

490 ms

webcomponents-loader.js

webcomponents-loader.js

16 ms

typo3-universe.js

typo3-universe.js

18 ms

randombanners.js

randombanners.js

288 ms

decode.js

decode.js

288 ms

require.js

require.js

416 ms

gtm.js

gtm.js

80 ms

logo_321e23daf0da84ce9fa99f78258d6ea4.1669194745.png

logo_321e23daf0da84ce9fa99f78258d6ea4.1669194745.png

651 ms

logo_bff66a9e1f471ec98a604b2b051845e2.1710246893.svg

logo_bff66a9e1f471ec98a604b2b051845e2.1710246893.svg

755 ms

logo.png

logo.png

849 ms

jweiland_logo_300x88.png

jweiland_logo_300x88.png

943 ms

logo_9ffda6e085e53b327f47f3ce8dd45925.1620304048.svg

logo_9ffda6e085e53b327f47f3ce8dd45925.1620304048.svg

948 ms

logo_dd8069805a3019104bf63e38f431d195.1637839382.svg

logo_dd8069805a3019104bf63e38f431d195.1637839382.svg

950 ms

logo_1ca0b419fdfe0d43b5880e57baf7981a.1682515184.svg

logo_1ca0b419fdfe0d43b5880e57baf7981a.1682515184.svg

950 ms

logo_a91067f39d64394542d0e525ca5a2d03.1643292353.png

logo_a91067f39d64394542d0e525ca5a2d03.1643292353.png

1044 ms

logo_30631cb68d080b6637f1b2940ea04b28.1679391896.svg

logo_30631cb68d080b6637f1b2940ea04b28.1679391896.svg

952 ms

logo_7957278b4ac6122f6dccb19bcb51bdad.1712591922.svg

logo_7957278b4ac6122f6dccb19bcb51bdad.1712591922.svg

1041 ms

logo_8c4f7b0106fd71a1b418a256f06139d8.1687436703.png

logo_8c4f7b0106fd71a1b418a256f06139d8.1687436703.png

1047 ms

logo-maxserv-zonder-groot.png

logo-maxserv-zonder-groot.png

1045 ms

logo_880d743eec23d6b7999582700871bdf7.1619453793.png

logo_880d743eec23d6b7999582700871bdf7.1619453793.png

1047 ms

blindwerk_schriftzug.png

blindwerk_schriftzug.png

1049 ms

typo3_logo.svg

typo3_logo.svg

132 ms

typo3_nomargins.svg

typo3_nomargins.svg

129 ms

csm_typo3-pagetree-screenshot-mock-up_984f8f3795.jpg

csm_typo3-pagetree-screenshot-mock-up_984f8f3795.jpg

193 ms

csm_6932872980_d788451b65_o_4e84bb9425.jpg

csm_6932872980_d788451b65_o_4e84bb9425.jpg

195 ms

csm_26276623101_a436d2f07a_o_270a7b2c42.jpg

csm_26276623101_a436d2f07a_o_270a7b2c42.jpg

131 ms

csm_startup-photos_3680a49e5f.jpg

csm_startup-photos_3680a49e5f.jpg

174 ms

csm_Header_blog_post_LAY01.1_a5eed74ce7.jpg

csm_Header_blog_post_LAY01.1_a5eed74ce7.jpg

500 ms

csm_v13_1_landing_page_slide_0a8641aa6d.jpg

csm_v13_1_landing_page_slide_0a8641aa6d.jpg

383 ms

csm_typo3_idea_bulb_853fce7682.jpg

csm_typo3_idea_bulb_853fce7682.jpg

201 ms

csm_T3DD24_TiketSale_Header_org_688ebe5b5b.jpg

csm_T3DD24_TiketSale_Header_org_688ebe5b5b.jpg

497 ms

csm_OpenWebsiteAlliance_Header_org_LAY02_9f2db4f5c4.jpg

csm_OpenWebsiteAlliance_Header_org_LAY02_9f2db4f5c4.jpg

381 ms

t3dd24_all_white.svg

t3dd24_all_white.svg

308 ms

youtube_play_button.svg

youtube_play_button.svg

311 ms

csm_9868818104_764b0c72e9_h_4721317855.jpg

csm_9868818104_764b0c72e9_h_4721317855.jpg

501 ms

000136-people-three-02.svg

000136-people-three-02.svg

390 ms

csm_pexels-photo-510259_9efd8589aa.jpeg

csm_pexels-photo-510259_9efd8589aa.jpeg

498 ms

000726-book-text.svg

000726-book-text.svg

499 ms

csm_pexels-photo-424517_d76103590f.jpeg

csm_pexels-photo-424517_d76103590f.jpeg

500 ms

002515-gift-heart.svg

002515-gift-heart.svg

542 ms

membership-logos_02.svg

membership-logos_02.svg

572 ms

piwik.js

piwik.js

634 ms

youtube_82e83b00f60be780a4c825b5bb810454.jpg

youtube_82e83b00f60be780a4c825b5bb810454.jpg

547 ms

webcomponents-sd-ce-pf.js

webcomponents-sd-ce-pf.js

324 ms

share-v8-latin-regular.woff

share-v8-latin-regular.woff

471 ms

share-v8-latin-700.woff

share-v8-latin-700.woff

471 ms

fa-solid-900.woff

fa-solid-900.woff

489 ms

SourceSansPro-Regular.otf.woff

SourceSansPro-Regular.otf.woff

624 ms

SourceSansPro-Light.otf.woff

SourceSansPro-Light.otf.woff

743 ms

SourceSansPro-Bold.otf.woff

SourceSansPro-Bold.otf.woff

654 ms

fa-brands-400.woff

fa-brands-400.woff

661 ms

analytics.js

analytics.js

16 ms

collect

collect

13 ms

js

js

61 ms

index.php

index.php

312 ms

index.php

index.php

307 ms

ajax-loader.gif

ajax-loader.gif

333 ms

main.js

main.js

363 ms

piwik.php

piwik.php

142 ms

tab-navigation-helper-1f5e2cd2.js

tab-navigation-helper-1f5e2cd2.js

97 ms

Accessibility Review

typo3.biz accessibility score

76

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

typo3.biz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

typo3.biz SEO score

90

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

Social Sharing Optimization

typo3.biz

Open Graph data is detected on the main page of TYPO3. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: