Tools & Wizards About Us
splitbrain.org screenshot

Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

splitbrain.org

Welcome [splitbrain.org]

Page Load Speed

2.3 sec in total

First Response

224 ms

Resources Loaded

1.7 sec

Page Rendered

313 ms

splitbrain.org screenshot

About Website

Click here to check amazing Splitbrain content for Bangladesh. Otherwise, check out these important facts you probably never knew about splitbrain.org

Andreas Gohr is a web developer and maker based in Berlin, Germany, sharing blog posts and links on his website, splitbrain.org.

Visit splitbrain.org

Key Findings

We analyzed Splitbrain.org page load time and found that the first response time was 224 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

splitbrain.org performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

75/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.226

55/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

splitbrain.org

224 ms

www.splitbrain.org

431 ms

css.php

199 ms

jquery.php

488 ms

js.php

483 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 69% of them (24 requests) were addressed to the original Splitbrain.org, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Splitbrain.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.1 kB (34%)

Content Size

644.4 kB

After Optimization

427.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Splitbrain.org main page is 644.4 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. 40% of websites need less resources to load. Images take 569.8 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 15.1 kB

  • Original 21.7 kB
  • After minification 20.5 kB
  • After compression 6.6 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 15.1 kB or 69% of the original size.

Image Optimization

-30%

Potential reduce by 170.1 kB

  • Original 569.8 kB
  • After minification 399.8 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, Splitbrain needs image optimization as it can save up to 170.1 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 32.0 kB

  • Original 52.9 kB
  • After minification 52.9 kB
  • After compression 20.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 32.0 kB or 60% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (13%)

Requests Now

30

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

splitbrain.org

splitbrain.org

224 ms

www.splitbrain.org

www.splitbrain.org

431 ms

css.php

css.php

199 ms

jquery.php

jquery.php

488 ms

js.php

js.php

483 ms

js

js

53 ms

css

css

28 ms

b6b4d7dbe3fb7cf61b68e36cd80f8698.jpg

b6b4d7dbe3fb7cf61b68e36cd80f8698.jpg

49 ms

black-thread-light.png

black-thread-light.png

97 ms

stanley.png

stanley.png

296 ms

fetch.php

fetch.php

318 ms

sections.png

sections.png

350 ms

sevrin.jpg

sevrin.jpg

451 ms

fetch.php

fetch.php

379 ms

img_20230716_072218.jpg

img_20230716_072218.jpg

496 ms

fetch.php

fetch.php

421 ms

pxl_20240125_151805137.jpg

pxl_20240125_151805137.jpg

544 ms

939d.png

939d.png

578 ms

fetch.php

fetch.php

525 ms

firewood1.jpg

firewood1.jpg

650 ms

fetch.php

fetch.php

601 ms

clamps1.jpg

clamps1.jpg

820 ms

fetch.php

fetch.php

649 ms

pxl_20231106_181014480.jpg

pxl_20231106_181014480.jpg

683 ms

solar.flow.png

solar.flow.png

705 ms

beer.svg

beer.svg

744 ms

taskrunner.php

taskrunner.php

754 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJBbMl1RMB.ttf

54 ms

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl1RMB.ttf

HhyJU5sn9vOmLxNkIwRSjTVNWLEJ0LQl1RMB.ttf

55 ms

js

js

48 ms

analytics.js

analytics.js

18 ms

N0bU2SZBIuF2PU_0A3Rw.ttf

N0bU2SZBIuF2PU_0A3Rw.ttf

9 ms

collect

collect

52 ms

collect

collect

38 ms

ga-audiences

ga-audiences

28 ms

Accessibility Review

splitbrain.org accessibility score

87

Accessibility Issues

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

splitbrain.org 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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

splitbrain.org SEO score

92

Search Engine Optimization Advices

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 Splitbrain.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 Splitbrain.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.

Social Sharing Optimization

splitbrain.org

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