Access studiobad.co. studio.bad architects - simple, modern, residential architecture.

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.9 s

0/100

25%

SI (Speed Index)

Value8.4 s

19/100

10%

TBT (Total Blocking Time)

Value1,520 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

studiobad.co

46 ms

GmztZ4Ee9FK9J7iSBy74r3jNuoCSGCIYnwhAZjAjOWwfezG2fFHN4UJLFRbh52jhWD9uFhmcZAZcZQsKw288FQmcFDsKwR8Kws7eMkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0-cmcZ148pPu3-AoGZA8kdkoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8OeT8ZcZkZWqlSe80-emTScv0SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYFXiAsTdh4yZfoRdkUaiaS0jAFu-WsoShFGZAsude80ZkoRdhXCiaiaOcBRiA8XpWFR-emqiAUTdcS0dcmXOYiaikoySkolZPUaiaS0-cmcZ148pPu3-AoGZA8kdkoDSWmyScmDSeBRZPoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCiaiaO1FXiAsTdh4yZfoRdkJwSY4zpe8ljPu0daZyJ68ciWsuScIlSYb7fbKzMsMMeMb6MKG4fJsmIMIjgfMfH6qJ6m9bMs6YJMJ7fbKfmsMgegI6MTMgtTrrx69.js

42 ms

css2

64 ms

legacy.js

23 ms

modern.js

24 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Studiobad.co, 16% (10 requests) were made to Assets.squarespace.com and 9% (6 requests) were made to User.lpcontent.net. The less responsive or slowest element that took the longest time to load (311 ms) relates to the external source Bimafterdark.lpages.co.

Content Size

1.4 MB

After Optimization

1.2 MB

In fact, the total size of Studiobad.co main page is 1.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 62.1 kB

Original 78.0 kB
After minification 70.2 kB
After compression 15.9 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 62.1 kB or 80% of the original size.

Image Optimization

-56%

Potential reduce by 38.4 kB

Original 68.9 kB
After minification 30.6 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, Studio Bad needs image optimization as it can save up to 38.4 kB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 42.9 kB

Original 1.1 MB
After minification 1.1 MB
After compression 1.1 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-59%

Potential reduce by 52.1 kB

Original 87.7 kB
After minification 87.6 kB
After compression 35.7 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. Studiobad.co needs all CSS files to be minified and compressed as it can save up to 52.1 kB or 59% of the original size.

Requests Now

After Optimization

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