Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

enginehouse.co

Coworking Spaces St Kilda & Balaclava, Melbourne - Engine House

Page Load Speed

4.1 sec in total

First Response

548 ms

Resources Loaded

3.3 sec

Page Rendered

268 ms

About Website

Welcome to enginehouse.co homepage info - get ready to check Engine House best content right away, or after learning these important things about enginehouse.co

Engine Houses are Melbourne coworking spaces that make you happy to come to work, feel creative while you’re here and leave with a sense of achievement.

Visit enginehouse.co

Key Findings

We analyzed Enginehouse.co page load time and found that the first response time was 548 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

enginehouse.co performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value26.1 s

0/100

25%

SI (Speed Index)

Value22.5 s

0/100

10%

TBT (Total Blocking Time)

Value5,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value33.7 s

0/100

10%

Network Requests Diagram

enginehouse.co

548 ms

enginehouse.co

1331 ms

omgf-stylesheet-276.css

28 ms

styles.css

31 ms

google-reviews.css

32 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 90% of them (113 requests) were addressed to the original Enginehouse.co, 2% (2 requests) were made to Assets.calendly.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Enginehouse.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 221.7 kB (5%)

Content Size

4.4 MB

After Optimization

4.2 MB

In fact, the total size of Enginehouse.co main page is 4.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. 80% 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. Images take 3.3 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 121.8 kB

  • Original 143.7 kB
  • After minification 139.9 kB
  • After compression 21.8 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 121.8 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 85.8 kB

  • Original 3.3 MB
  • After minification 3.2 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. Engine House images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 8.5 kB

  • Original 747.1 kB
  • After minification 746.8 kB
  • After compression 738.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. This website has mostly compressed JavaScripts.

CSS Optimization

-3%

Potential reduce by 5.6 kB

  • Original 194.2 kB
  • After minification 193.4 kB
  • After compression 188.6 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. Enginehouse.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 102 (84%)

Requests Now

121

After Optimization

19

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

Accessibility Review

enginehouse.co accessibility score

85

Accessibility Issues

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

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

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

enginehouse.co best practices score

75

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

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

enginehouse.co SEO score

86

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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

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 Enginehouse.co 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 Enginehouse.co 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

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