Tools & Wizards About Us
forge.co.nz screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

forge.co.nz

Forge Creative | Website Designers | Development & Web Design Agency Auckland NZ

Page Load Speed

18.1 sec in total

First Response

1.1 sec

Resources Loaded

16.9 sec

Page Rendered

137 ms

forge.co.nz screenshot

About Website

Visit forge.co.nz now to see the best up-to-date Forge content and also check out these interesting facts you probably never knew about forge.co.nz

Forge Creative is a full-service Web Design Agency. Providing Branding, Web Development, Graphic Design, & Digital Marketing in Auckland, New Zealand.

Visit forge.co.nz

Key Findings

We analyzed Forge.co.nz page load time and found that the first response time was 1.1 sec and then it took 17 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

forge.co.nz performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.5 s

2/100

10%

LCP (Largest Contentful Paint)

Value10.1 s

0/100

25%

SI (Speed Index)

Value12.9 s

2/100

10%

TBT (Total Blocking Time)

Value1,930 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

5/100

10%

Network Requests Diagram

forge.co.nz

1098 ms

rangeslider.css

219 ms

bootstrap.min.css

39 ms

all.css

436 ms

main.css

875 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 70% of them (35 requests) were addressed to the original Forge.co.nz, 12% (6 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (8.4 sec) belongs to the original domain Forge.co.nz.

Page Optimization Overview & Recommendations

Page size can be reduced by 597.0 kB (50%)

Content Size

1.2 MB

After Optimization

594.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Forge.co.nz main page is 1.2 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. CSS take 604.0 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 122.2 kB

  • Original 137.8 kB
  • After minification 133.0 kB
  • After compression 15.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 122.2 kB or 89% of the original size.

Image Optimization

-7%

Potential reduce by 6.8 kB

  • Original 103.5 kB
  • After minification 96.7 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. Forge images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.6 kB

  • Original 346.4 kB
  • After minification 346.4 kB
  • After compression 343.8 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

-77%

Potential reduce by 465.4 kB

  • Original 604.0 kB
  • After minification 563.8 kB
  • After compression 138.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. Forge.co.nz needs all CSS files to be minified and compressed as it can save up to 465.4 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (78%)

Requests Now

40

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

forge.co.nz

forge.co.nz

1098 ms

rangeslider.css

rangeslider.css

219 ms

bootstrap.min.css

bootstrap.min.css

39 ms

all.css

all.css

436 ms

main.css

main.css

875 ms

css

css

83 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

32 ms

bootstrap.min.js

bootstrap.min.js

48 ms

rangeslider.min.js

rangeslider.min.js

858 ms

main.js

main.js

859 ms

css

css

100 ms

formidableforms.css

formidableforms.css

1076 ms

layerslider.css

layerslider.css

869 ms

style.min.css

style.min.css

1086 ms

cleantalk-public.min.css

cleantalk-public.min.css

1071 ms

style.css

style.css

1072 ms

custom-slider.css

custom-slider.css

1085 ms

js_composer.min.css

js_composer.min.css

1100 ms

jquery.min.js

jquery.min.js

1501 ms

jquery-migrate.min.js

jquery-migrate.min.js

1286 ms

layerslider.utils.js

layerslider.utils.js

1511 ms

layerslider.kreaturamedia.jquery.js

layerslider.kreaturamedia.jquery.js

1737 ms

layerslider.transitions.js

layerslider.transitions.js

1302 ms

apbct-public-bundle.min.js

apbct-public-bundle.min.js

1319 ms

navigation.js

navigation.js

1498 ms

skip-link-focus-fix.js

skip-link-focus-fix.js

1528 ms

custom-slider.js

custom-slider.js

1535 ms

gsap.min.js

gsap.min.js

39 ms

frm.min.js

frm.min.js

8430 ms

api.js

api.js

48 ms

js_composer_front.min.js

js_composer_front.min.js

1715 ms

lazyload.min.js

lazyload.min.js

1724 ms

css2

css2

16 ms

gtm.js

gtm.js

63 ms

forge-creative-logo-sprite.png

forge-creative-logo-sprite.png

219 ms

forge-menu-sprite.png

forge-menu-sprite.png

218 ms

forge-speech-bubble-sprite.png

forge-speech-bubble-sprite.png

217 ms

close.png

close.png

217 ms

close-teal.png

close-teal.png

219 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

52 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

53 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

68 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

74 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

75 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVQ.woff

75 ms

fa-solid-900.woff

fa-solid-900.woff

6613 ms

fa-regular-400.woff

fa-regular-400.woff

367 ms

fa-brands-400.woff

fa-brands-400.woff

6612 ms

text-wave-bg.svg

text-wave-bg.svg

370 ms

wave-grey.png

wave-grey.png

6590 ms

Accessibility Review

forge.co.nz accessibility score

55

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

High

ARIA IDs are not unique

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

High

Form elements do not have associated labels

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

[id] attributes on active, focusable elements are not unique

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

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

forge.co.nz 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

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

forge.co.nz 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 Forge.co.nz 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 Forge.co.nz 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

forge.co.nz

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