Tools & Wizards About Us
wesolv.co screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

wesolv.co

WeSolv | Connecting Diverse MBAs with Top Companies

Page Load Speed

2.2 sec in total

First Response

14 ms

Resources Loaded

1.6 sec

Page Rendered

541 ms

wesolv.co screenshot

About Website

Click here to check amazing We Solv content. Otherwise, check out these important facts you probably never knew about wesolv.co

WeSolv connects companies to the largest network of diverse MBAs through real projects to assess actual skills and find the best candidates.

Visit wesolv.co

Key Findings

We analyzed Wesolv.co page load time and found that the first response time was 14 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wesolv.co performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value5,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value23.6 s

1/100

10%

Network Requests Diagram

wesolv.co

14 ms

www.wesolv.com

330 ms

all.css

51 ms

autoptimize_d175323609b81bd35913be8f25bb2559.css

338 ms

js

95 ms

Our browser made a total of 88 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Wesolv.co, 45% (40 requests) were made to Wesolv.com and 17% (15 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (603 ms) relates to the external source Wesolv.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 107.5 kB (9%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wesolv.co 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. 50% of websites need less resources to load. Images take 668.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 71.4 kB

  • Original 90.0 kB
  • After minification 89.8 kB
  • After compression 18.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 71.4 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 28.6 kB

  • Original 668.2 kB
  • After minification 639.6 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. We Solv images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 7.5 kB

  • Original 350.2 kB
  • After minification 350.2 kB
  • After compression 342.7 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

-0%

Potential reduce by 0 B

  • Original 129.0 kB
  • After minification 129.0 kB
  • After compression 129.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. Wesolv.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 35 (51%)

Requests Now

69

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wesolv.co

wesolv.co

14 ms

www.wesolv.com

www.wesolv.com

330 ms

all.css

all.css

51 ms

autoptimize_d175323609b81bd35913be8f25bb2559.css

autoptimize_d175323609b81bd35913be8f25bb2559.css

338 ms

js

js

95 ms

css

css

62 ms

css

css

88 ms

jquery.min.js

jquery.min.js

288 ms

all.css

all.css

64 ms

v2.js

v2.js

97 ms

2882134.js

2882134.js

118 ms

2882134.js

2882134.js

153 ms

e-202440.js

e-202440.js

41 ms

autoptimize_db51298df5a2a54cb50f81b160c4224b.js

autoptimize_db51298df5a2a54cb50f81b160c4224b.js

577 ms

gtm.js

gtm.js

107 ms

roundtrip.js

roundtrip.js

301 ms

Logo_WeSolv.png

Logo_WeSolv.png

131 ms

hero-banner-min.jpg

hero-banner-min.jpg

186 ms

accenturev1.png

accenturev1.png

190 ms

harvard-1.png

harvard-1.png

230 ms

bank-of-america.png

bank-of-america.png

241 ms

kellogg-1.png

kellogg-1.png

239 ms

mit-management-1.png

mit-management-1.png

241 ms

Discover-1.png

Discover-1.png

239 ms

marshall-1.png

marshall-1.png

242 ms

ita-small.png

ita-small.png

283 ms

Play_video_button-min.jpg

Play_video_button-min.jpg

291 ms

home-blurb-process-1-min.png

home-blurb-process-1-min.png

292 ms

process-Arrow-min-e1556231149324.png

process-Arrow-min-e1556231149324.png

293 ms

home-blurb-process-2-min.png

home-blurb-process-2-min.png

293 ms

process-Arrow-min.png

process-Arrow-min.png

295 ms

home-blurb-process-3-min.png

home-blurb-process-3-min.png

336 ms

home-blurb-process-4-min.png

home-blurb-process-4-min.png

344 ms

test-slider-bg-min.jpg

test-slider-bg-min.jpg

345 ms

element_new_f4f2f2-min.png

element_new_f4f2f2-min.png

347 ms

check-min_blue.png

check-min_blue.png

346 ms

check-min.png

check-min.png

348 ms

Lightbulbs_elements-left.png

Lightbulbs_elements-left.png

387 ms

1.png

1.png

551 ms

2.png

2.png

473 ms

3.png

3.png

550 ms

4.png

4.png

550 ms

forbes.png

forbes.png

400 ms

Geek_Wire.png

Geek_Wire.png

469 ms

venture-beat.png

venture-beat.png

475 ms

the-seattle.png

the-seattle.png

552 ms

build-inchicago.png

build-inchicago.png

549 ms

Techstars_logo-white.png

Techstars_logo-white.png

551 ms

footer-logo-v12.png

footer-logo-v12.png

603 ms

font

font

69 ms

font

font

90 ms

modules.woff

modules.woff

540 ms

modules.woff

modules.woff

539 ms

collectedforms.js

collectedforms.js

114 ms

banner.js

banner.js

70 ms

fb.js

fb.js

68 ms

web-interactives-embed.js

web-interactives-embed.js

118 ms

2882134.js

2882134.js

68 ms

AUUIHOBCGNGKTJFPBAM77Y

AUUIHOBCGNGKTJFPBAM77Y

17 ms

fbevents.js

fbevents.js

29 ms

out

out

6 ms

AO4QZNAMORDHFDV4XBPWZV

AO4QZNAMORDHFDV4XBPWZV

6 ms

out

out

8 ms

out

out

9 ms

out

out

45 ms

out

out

12 ms

out

out

11 ms

out

out

11 ms

out

out

16 ms

out

out

47 ms

out

out

48 ms

out

out

47 ms

out

out

47 ms

trigger

trigger

68 ms

tap.php

tap.php

125 ms

Pug

Pug

128 ms

pixel

pixel

25 ms

sd

sd

16 ms

xuid

xuid

6 ms

sync

sync

21 ms

generic

generic

17 ms

in

in

9 ms

rum

rum

30 ms

generic

generic

4 ms

receive

receive

31 ms

bounce

bounce

28 ms

autoptimize_ac9d2b94e05d672cb538c84f835350fe.css

autoptimize_ac9d2b94e05d672cb538c84f835350fe.css

57 ms

wstm1qbk

wstm1qbk

17 ms

Accessibility Review

wesolv.co accessibility score

84

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

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

wesolv.co 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

wesolv.co SEO score

93

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

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 Wesolv.co 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 Wesolv.co 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

wesolv.co

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