Tools & Wizards About Us
weareninetwenty.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

weareninetwenty.com

Nine Twenty | Boutique Recruitment Agency | Glasgow & Edinburgh

Page Load Speed

3.6 sec in total

First Response

210 ms

Resources Loaded

2.3 sec

Page Rendered

1.1 sec

weareninetwenty.com screenshot

About Website

Welcome to weareninetwenty.com homepage info - get ready to check Weare Nine Twenty best content for United Kingdom right away, or after learning these important things about weareninetwenty.com

Nine Twenty are a boutique multi-sector recruitment agency specialising in Technology, Engineering & Manufacturing and Accountancy & Finance. Based in Glasgow, we also operate in Edinburgh and the cen...

Visit weareninetwenty.com

Key Findings

We analyzed Weareninetwenty.com page load time and found that the first response time was 210 ms and then it took 3.4 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

weareninetwenty.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value16.5 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

weareninetwenty.com

210 ms

www.weareninetwenty.com

192 ms

www.weareninetwenty.com

428 ms

layout.min.css

98 ms

custom.min.css

290 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 69% of them (33 requests) were addressed to the original Weareninetwenty.com, 10% (5 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (915 ms) belongs to the original domain Weareninetwenty.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (65%)

Content Size

2.9 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-80%

Potential reduce by 44.7 kB

  • Original 56.0 kB
  • After minification 52.1 kB
  • After compression 11.3 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 44.7 kB or 80% of the original size.

Image Optimization

-78%

Potential reduce by 1.6 MB

  • Original 2.1 MB
  • After minification 453.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. Obviously, Weare Nine Twenty needs image optimization as it can save up to 1.6 MB or 78% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-26%

Potential reduce by 150.0 kB

  • Original 572.0 kB
  • After minification 572.0 kB
  • After compression 422.0 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 150.0 kB or 26% of the original size.

CSS Optimization

-27%

Potential reduce by 43.4 kB

  • Original 160.2 kB
  • After minification 160.2 kB
  • After compression 116.8 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. Weareninetwenty.com needs all CSS files to be minified and compressed as it can save up to 43.4 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (71%)

Requests Now

35

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weareninetwenty.com

weareninetwenty.com

210 ms

www.weareninetwenty.com

www.weareninetwenty.com

192 ms

www.weareninetwenty.com

www.weareninetwenty.com

428 ms

layout.min.css

layout.min.css

98 ms

custom.min.css

custom.min.css

290 ms

jobsearch.min.css

jobsearch.min.css

334 ms

blogs.min.css

blogs.min.css

332 ms

chosen.min.css

chosen.min.css

333 ms

main.min.css

main.min.css

514 ms

6c18729ff3.js

6c18729ff3.js

48 ms

Calendar.min.css

Calendar.min.css

331 ms

custom-css.css

custom-css.css

371 ms

typography.css

typography.css

413 ms

ffCore.min.js

ffCore.min.js

594 ms

73b37871d15ff56dd4da20d886438c66.js

73b37871d15ff56dd4da20d886438c66.js

414 ms

js

js

69 ms

aspNetFramework.min.js

aspNetFramework.min.js

691 ms

application_universal.js

application_universal.js

900 ms

application.js

application.js

679 ms

chosen.jquery.min.js

chosen.jquery.min.js

499 ms

jquery.chained.min.js

jquery.chained.min.js

592 ms

jquery.nicefileinput.min.js

jquery.nicefileinput.min.js

594 ms

main.js

main.js

665 ms

firefish.js

firefish.js

668 ms

css

css

35 ms

css2

css2

20 ms

fbevents.js

fbevents.js

21 ms

iptrack.js

iptrack.js

511 ms

hotjar-2866997.js

hotjar-2866997.js

97 ms

Home%20Graphic%20Sample%201.png

Home%20Graphic%20Sample%201.png

872 ms

Home%20Graphic%20Sample%202.png

Home%20Graphic%20Sample%202.png

915 ms

NT%20Group%20White%20-%20Copy.png

NT%20Group%20White%20-%20Copy.png

504 ms

NT%20Group%20White%20Website.png

NT%20Group%20White%20Website.png

311 ms

Home%20Page%20File%20Graphic%20Left.jpg

Home%20Page%20File%20Graphic%20Left.jpg

539 ms

Home%20Page%20File%20Graphic%20Right%202.png

Home%20Page%20File%20Graphic%20Right%202.png

540 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

220 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

220 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

260 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

273 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

272 ms

fa-brands-400.ttf

fa-brands-400.ttf

259 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

215 ms

fa-regular-400.ttf

fa-regular-400.ttf

374 ms

fa-solid-900.ttf

fa-solid-900.ttf

375 ms

insight.min.js

insight.min.js

261 ms

who.ashx

who.ashx

122 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

85 ms

insight_tag_errors.gif

insight_tag_errors.gif

120 ms

Accessibility Review

weareninetwenty.com accessibility score

69

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

weareninetwenty.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

weareninetwenty.com SEO score

98

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

weareninetwenty.com

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