Tools & Wizards About Us
bandwidth.team screenshot

Report Summary

  • 19

    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
    57% of websites

  • 86

    SEO

    Google-friendlier than
    61% of websites

bandwidth.team

Seattle Recruiting, Staffing & Talent Acquisition | Bandwidth

Page Load Speed

8.7 sec in total

First Response

129 ms

Resources Loaded

8 sec

Page Rendered

634 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 129 ms and then it took 8.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

bandwidth.team performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value14.4 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value5,230 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.3 s

9/100

10%

Network Requests Diagram

bandwidth.team

129 ms

bandwidth.team

2738 ms

js

298 ms

gtm.js

495 ms

wp-emoji-release.min.js

129 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 158.9 kB (13%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bandwidth.team 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. 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 711.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 141.7 kB

  • Original 172.0 kB
  • After minification 170.8 kB
  • After compression 30.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 141.7 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 5.5 kB

  • Original 711.4 kB
  • After minification 705.9 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. Bandwidth images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.8 kB

  • Original 114.8 kB
  • After minification 114.8 kB
  • After compression 112.1 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 8.9 kB

  • Original 214.9 kB
  • After minification 214.9 kB
  • After compression 206.0 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 57 (84%)

Requests Now

68

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 68 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 32 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

bandwidth.team

bandwidth.team

129 ms

bandwidth.team

bandwidth.team

2738 ms

js

js

298 ms

gtm.js

gtm.js

495 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

129 ms

style.min.css

style.min.css

319 ms

animate-animo.css

animate-animo.css

452 ms

styles.css

styles.css

425 ms

font-awesome.min.css

font-awesome.min.css

289 ms

Defaults.css

Defaults.css

414 ms

js_composer_front_custom.css

js_composer_front_custom.css

654 ms

pum-site-styles.css

pum-site-styles.css

432 ms

css

css

610 ms

main.min.css

main.min.css

507 ms

icomoon-the7-font.min.css

icomoon-the7-font.min.css

799 ms

all.min.css

all.min.css

836 ms

back-compat.min.css

back-compat.min.css

816 ms

fontello.min.css

fontello.min.css

809 ms

post-type.min.css

post-type.min.css

799 ms

custom.css

custom.css

1443 ms

media.css

media.css

1424 ms

mega-menu.css

mega-menu.css

1393 ms

the7-elements-albums-portfolio.css

the7-elements-albums-portfolio.css

1396 ms

post-type-dynamic.css

post-type-dynamic.css

1399 ms

style.css

style.css

1393 ms

style.min.css

style.min.css

1488 ms

jquery.min.js

jquery.min.js

1578 ms

jquery-migrate.min.js

jquery-migrate.min.js

1559 ms

above-the-fold.min.js

above-the-fold.min.js

1546 ms

ultimate-params.min.js

ultimate-params.min.js

1545 ms

2266.css

2266.css

1559 ms

1932.css

1932.css

1560 ms

animate.min.css

animate.min.css

1550 ms

css

css

585 ms

background-style.min.css

background-style.min.css

1542 ms

main.min.js

main.min.js

1908 ms

animo.min.js

animo.min.js

1552 ms

jquery.ba-throttle-debounce.min.js

jquery.ba-throttle-debounce.min.js

1553 ms

viewportchecker.js

viewportchecker.js

1554 ms

edsanimate.js

edsanimate.js

1554 ms

edsanimate.site.js

edsanimate.site.js

1531 ms

index.js

index.js

1864 ms

api.js

api.js

703 ms

index.js

index.js

1858 ms

page-scroll-to-id.min.js

page-scroll-to-id.min.js

1762 ms

analytics.js

analytics.js

642 ms

akismet-frontend.js

akismet-frontend.js

1631 ms

js

js

452 ms

core.min.js

core.min.js

1496 ms

css

css

410 ms

pum-site-scripts.js

pum-site-scripts.js

1517 ms

post-type.min.js

post-type.min.js

1449 ms

wpcf7-recaptcha-controls.js

wpcf7-recaptcha-controls.js

1428 ms

js_composer_front.min.js

js_composer_front.min.js

1320 ms

vc-waypoints.min.js

vc-waypoints.min.js

1176 ms

jquery-appear.min.js

jquery-appear.min.js

1129 ms

ultimate_bg.min.js

ultimate_bg.min.js

1123 ms

custom.min.js

custom.min.js

1106 ms

skrollr.min.js

skrollr.min.js

1100 ms

1925.js

1925.js

1102 ms

collect

collect

1029 ms

logo-2.png

logo-2.png

497 ms

webnc-web.png

webnc-web.png

520 ms

Astra-web.png

Astra-web.png

492 ms

AvenirLTStd-Book.woff

AvenirLTStd-Book.woff

328 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

1197 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

1198 ms

AvenirLTStd-Heavy.woff

AvenirLTStd-Heavy.woff

323 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

1201 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

1193 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

1231 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff

1183 ms

AvenirLTStd-Black.woff

AvenirLTStd-Black.woff

305 ms

pexels-cowomen-2041627-min-scaled.jpg

pexels-cowomen-2041627-min-scaled.jpg

1166 ms

footerback.jpg

footerback.jpg

1093 ms

fa-solid-900.woff

fa-solid-900.woff

975 ms

fa-regular-400.woff

fa-regular-400.woff

973 ms

fa-brands-400.woff

fa-brands-400.woff

976 ms

AvenirLTStd-Medium.woff

AvenirLTStd-Medium.woff

674 ms

icomoon-the7-font.ttf

icomoon-the7-font.ttf

673 ms

recaptcha__en.js

recaptcha__en.js

443 ms

sss-1.jpg

sss-1.jpg

268 ms

quotes.png

quotes.png

170 ms

logo2.png

logo2.png

170 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: