Tools & Wizards About Us
project3.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

project3.com

Project3 | Events. Marketing. Sponsorship | Perth, Western Australia

Page Load Speed

6.6 sec in total

First Response

834 ms

Resources Loaded

5.6 sec

Page Rendered

181 ms

project3.com screenshot

About Website

Click here to check amazing Project3 content. Otherwise, check out these important facts you probably never knew about project3.com

Project3 is one of Western Australia’s leading events and marketing consultancies, executing projects across the state from offices in O’Connor.

Visit project3.com

Key Findings

We analyzed Project3.com page load time and found that the first response time was 834 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

project3.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

50/100

10%

LCP (Largest Contentful Paint)

Value7.6 s

3/100

25%

SI (Speed Index)

Value7.6 s

26/100

10%

TBT (Total Blocking Time)

Value180 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.01

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

project3.com

834 ms

project3.com

1235 ms

bricks-advanced-themer.css

247 ms

cleantalk-public.min.css

492 ms

frontend-light.min.css

736 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 93% of them (43 requests) were addressed to the original Project3.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Project3.com.

Page Optimization Overview & Recommendations

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

Content Size

3.8 MB

After Optimization

3.7 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Project3.com main page is 3.8 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. 45% of websites need less resources to load. Images take 3.7 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 70.1 kB

  • Original 86.1 kB
  • After minification 84.8 kB
  • After compression 16.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. 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 70.1 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 33.2 kB

  • Original 3.7 MB
  • After minification 3.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. Project3 images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

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

Requests Breakdown

Number of requests can be reduced by 18 (46%)

Requests Now

39

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

project3.com

project3.com

834 ms

project3.com

project3.com

1235 ms

bricks-advanced-themer.css

bricks-advanced-themer.css

247 ms

cleantalk-public.min.css

cleantalk-public.min.css

492 ms

frontend-light.min.css

frontend-light.min.css

736 ms

style.css

style.css

742 ms

global-custom-css.min.css

global-custom-css.min.css

747 ms

theme-style-global.min.css

theme-style-global.min.css

753 ms

post-87.min.css

post-87.min.css

755 ms

post-55.min.css

post-55.min.css

983 ms

post-115.min.css

post-115.min.css

987 ms

font-awesome-6.min.css

font-awesome-6.min.css

1234 ms

jquery.min.js

jquery.min.js

1271 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

1276 ms

ct-bot-detector-wrapper.js

ct-bot-detector-wrapper.js

1004 ms

animate.min.css

animate.min.css

1229 ms

splide.min.css

splide.min.css

1265 ms

bricks.min.js

bricks.min.js

1509 ms

splide.min.js

splide.min.js

1478 ms

lazyload.min.js

lazyload.min.js

1481 ms

analytics.js

analytics.js

50 ms

Hero-4_web.jpg

Hero-4_web.jpg

732 ms

PublicSans-ExtraLight.ttf

PublicSans-ExtraLight.ttf

499 ms

PublicSans-Regular.ttf

PublicSans-Regular.ttf

739 ms

PublicSans-SemiBold.ttf

PublicSans-SemiBold.ttf

698 ms

PublicSans-Bold.ttf

PublicSans-Bold.ttf

701 ms

PublicSans-Black.ttf

PublicSans-Black.ttf

735 ms

collect

collect

13 ms

js

js

62 ms

SHOTBYTHOM-09827.jpg

SHOTBYTHOM-09827.jpg

784 ms

66-SHORELEAVE-DAY2-WESTBEACHSTUDIO.jpg

66-SHORELEAVE-DAY2-WESTBEACHSTUDIO.jpg

1220 ms

20170903_Shinju_0902.jpg

20170903_Shinju_0902.jpg

1221 ms

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-4.jpg

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-4.jpg

746 ms

2019-Coogee-Live-by-JR_145.jpg

2019-Coogee-Live-by-JR_145.jpg

1282 ms

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-20.jpg

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-20.jpg

1277 ms

HAYT3480.jpg

HAYT3480.jpg

994 ms

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-24.jpg

2020-Shinju-Long-Table-Dinner-@julia_rau_photography-low-res-24.jpg

1282 ms

io-anzacalbany-day2-086.jpg

io-anzacalbany-day2-086.jpg

1243 ms

SHOTBYTHOM-2020-1050456.jpg

SHOTBYTHOM-2020-1050456.jpg

1471 ms

SHOTBYTHOM-07923.jpg

SHOTBYTHOM-07923.jpg

1713 ms

SHOTBYTHOM-09261.jpg

SHOTBYTHOM-09261.jpg

1500 ms

5-WESTBEACHSTUDIO-SHINJU-LANTERNS.jpg

5-WESTBEACHSTUDIO-SHINJU-LANTERNS.jpg

1771 ms

0016-PADDOCKTOPLATE-SHORELEAVE-WESTBEACHSTUDIO.jpg

0016-PADDOCKTOPLATE-SHORELEAVE-WESTBEACHSTUDIO.jpg

1542 ms

26-WESTBEACHSTUDIO-SHINJU-LANTERNS.jpg

26-WESTBEACHSTUDIO-SHINJU-LANTERNS.jpg

1779 ms

40-WESTBEACHSTUDIO-SHORELEAVE-CLOSINGCEREMONY.jpg

40-WESTBEACHSTUDIO-SHORELEAVE-CLOSINGCEREMONY.jpg

1722 ms

0052-PADDOCKTOPLATE-SHORELEAVE-WESTBEACHSTUDIO.jpg

0052-PADDOCKTOPLATE-SHORELEAVE-WESTBEACHSTUDIO.jpg

1993 ms

Accessibility Review

project3.com accessibility score

98

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.

Best Practices

project3.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

project3.com SEO score

100

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

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 Project3.com 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 Project3.com 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

project3.com

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