Tools & Wizards About Us
bandwidth.team screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

bandwidth.team

Seattle Recruiting, Staffing & Talent Acquisition | Bandwidth

Page Load Speed

3.5 sec in total

First Response

124 ms

Resources Loaded

2.9 sec

Page Rendered

419 ms

bandwidth.team screenshot

About Website

Click here to check amazing Bandwidth content. Otherwise, check out these important facts you probably never knew about bandwidth.team

"Recruiting the right talent is key for business growth. Let our team at Bandwidth, a Seattle recruiting and staffing company, deliver the best candidate for you"

Visit bandwidth.team

Key Findings

We analyzed Bandwidth.team page load time and found that the first response time was 124 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 55% of websites can load faster.

Performance Metrics

bandwidth.team performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value15.4 s

0/100

25%

SI (Speed Index)

Value10.7 s

7/100

10%

TBT (Total Blocking Time)

Value3,960 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

bandwidth.team

124 ms

bandwidth.team

1125 ms

js

76 ms

gtm.js

114 ms

wp-emoji-release.min.js

74 ms

Our browser made a total of 89 requests to load all elements on the main page. We found that 81% of them (72 requests) were addressed to the original Bandwidth.team, 7% (6 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Bandwidth.team.

Page Optimization Overview & Recommendations

Page size can be reduced by 169.6 kB (10%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bandwidth.team main page is 1.7 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. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 143.7 kB

  • Original 174.5 kB
  • After minification 173.2 kB
  • After compression 30.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 143.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 14.1 kB

  • Original 1.0 MB
  • After minification 1.0 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. Bandwidth images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 247.5 kB
  • After minification 247.5 kB
  • After compression 244.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

-4%

Potential reduce by 9.1 kB

  • Original 216.3 kB
  • After minification 216.2 kB
  • After compression 207.2 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. Bandwidth.team has all CSS files already compressed.

Requests Breakdown

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

Requests Now

73

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bandwidth.team

bandwidth.team

124 ms

bandwidth.team

bandwidth.team

1125 ms

js

js

76 ms

gtm.js

gtm.js

114 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

74 ms

style.min.css

style.min.css

128 ms

block-style.css

block-style.css

195 ms

classic-themes.min.css

classic-themes.min.css

195 ms

animate-animo.css

animate-animo.css

199 ms

styles.css

styles.css

195 ms

font-awesome.min.css

font-awesome.min.css

38 ms

Defaults.css

Defaults.css

196 ms

js_composer_front_custom.css

js_composer_front_custom.css

268 ms

pum-site-styles.css

pum-site-styles.css

231 ms

css

css

40 ms

main.min.css

main.min.css

245 ms

icomoon-the7-font.min.css

icomoon-the7-font.min.css

234 ms

all.min.css

all.min.css

236 ms

back-compat.min.css

back-compat.min.css

241 ms

fontello.min.css

fontello.min.css

290 ms

post-type.min.css

post-type.min.css

292 ms

custom.css

custom.css

295 ms

media.css

media.css

341 ms

mega-menu.css

mega-menu.css

304 ms

the7-elements-albums-portfolio.css

the7-elements-albums-portfolio.css

305 ms

post-type-dynamic.css

post-type-dynamic.css

336 ms

style.css

style.css

337 ms

style.min.css

style.min.css

343 ms

jquery.min.js

jquery.min.js

353 ms

jquery-migrate.min.js

jquery-migrate.min.js

353 ms

above-the-fold.min.js

above-the-fold.min.js

388 ms

ultimate-params.min.js

ultimate-params.min.js

403 ms

2266.css

2266.css

409 ms

1932.css

1932.css

410 ms

animate.min.css

animate.min.css

426 ms

css

css

65 ms

background-style.min.css

background-style.min.css

426 ms

main.min.js

main.min.js

722 ms

animo.min.js

animo.min.js

476 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

477 ms

viewportchecker.js

viewportchecker.js

478 ms

edsanimate.js

edsanimate.js

479 ms

api.js

api.js

42 ms

edsanimate.site.js

edsanimate.site.js

478 ms

js

js

63 ms

analytics.js

analytics.js

39 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

432 ms

js

js

49 ms

collect

collect

26 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

384 ms

wp-polyfill.min.js

wp-polyfill.min.js

333 ms

index.js

index.js

332 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

330 ms

akismet-frontend.js

akismet-frontend.js

358 ms

core.min.js

core.min.js

374 ms

css

css

58 ms

pum-site-scripts.js

pum-site-scripts.js

343 ms

post-type.min.js

post-type.min.js

341 ms

wpcf7-recaptcha-controls.js

wpcf7-recaptcha-controls.js

334 ms

js_composer_front.min.js

js_composer_front.min.js

363 ms

vc-waypoints.min.js

vc-waypoints.min.js

340 ms

jquery-appear.min.js

jquery-appear.min.js

340 ms

ultimate_bg.min.js

ultimate_bg.min.js

337 ms

custom.min.js

custom.min.js

337 ms

skrollr.min.js

skrollr.min.js

355 ms

1925.js

1925.js

375 ms

logo-2.png

logo-2.png

271 ms

pexels-cowomen-2041627-min-scaled.jpg

pexels-cowomen-2041627-min-scaled.jpg

630 ms

footerback.jpg

footerback.jpg

255 ms

webnc-web.png

webnc-web.png

449 ms

Astra-web.png

Astra-web.png

383 ms

AvenirLTStd-Book.woff

AvenirLTStd-Book.woff

337 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

40 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

49 ms

AvenirLTStd-Heavy.woff

AvenirLTStd-Heavy.woff

327 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

71 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

73 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

71 ms

AvenirLTStd-Black.woff

AvenirLTStd-Black.woff

334 ms

fa-solid-900.woff

fa-solid-900.woff

571 ms

fa-regular-400.woff

fa-regular-400.woff

336 ms

fa-brands-400.woff

fa-brands-400.woff

571 ms

AvenirLTStd-Medium.woff

AvenirLTStd-Medium.woff

538 ms

icomoon-the7-font.ttf

icomoon-the7-font.ttf

539 ms

sss-1.jpg

sss-1.jpg

101 ms

quotes.png

quotes.png

101 ms

logo2.png

logo2.png

101 ms

pexels-thirdman-8485646.jpg

pexels-thirdman-8485646.jpg

466 ms

Accessibility Review

bandwidth.team accessibility score

73

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

Image elements do not have [alt] attributes

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.

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

bandwidth.team 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

bandwidth.team SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Bandwidth.team 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 Bandwidth.team 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

bandwidth.team

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