Tools & Wizards About Us
wesolv.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% 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.com

WeSolv | Connecting Diverse MBAs with Top Companies

Page Load Speed

2.2 sec in total

First Response

111 ms

Resources Loaded

1.5 sec

Page Rendered

538 ms

wesolv.com screenshot

About Website

Visit wesolv.com now to see the best up-to-date We Solv content and also check out these interesting facts you probably never knew about wesolv.com

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

Visit wesolv.com

Key Findings

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

Performance Metrics

wesolv.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value9.1 s

1/100

25%

SI (Speed Index)

Value7.8 s

24/100

10%

TBT (Total Blocking Time)

Value3,110 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value22.7 s

1/100

10%

Network Requests Diagram

wesolv.com

111 ms

wesolv.com

283 ms

all.css

49 ms

autoptimize_d175323609b81bd35913be8f25bb2559.css

183 ms

js

94 ms

Our browser made a total of 108 requests to load all elements on the main page. We found that 38% of them (41 requests) were addressed to the original Wesolv.com, 19% (21 requests) were made to Fonts.gstatic.com and 14% (15 requests) were made to D.adroll.com. The less responsive or slowest element that took the longest time to load (600 ms) belongs to the original domain Wesolv.com.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Wesolv.com 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. 70% 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.3 kB

  • Original 89.9 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.3 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.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

67

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 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.com

wesolv.com

111 ms

wesolv.com

wesolv.com

283 ms

all.css

all.css

49 ms

autoptimize_d175323609b81bd35913be8f25bb2559.css

autoptimize_d175323609b81bd35913be8f25bb2559.css

183 ms

js

js

94 ms

css

css

54 ms

css

css

70 ms

jquery.min.js

jquery.min.js

232 ms

all.css

all.css

55 ms

v2.js

v2.js

67 ms

2882134.js

2882134.js

83 ms

2882134.js

2882134.js

101 ms

e-202440.js

e-202440.js

42 ms

autoptimize_db51298df5a2a54cb50f81b160c4224b.js

autoptimize_db51298df5a2a54cb50f81b160c4224b.js

436 ms

gtm.js

gtm.js

108 ms

roundtrip.js

roundtrip.js

362 ms

Logo_WeSolv.png

Logo_WeSolv.png

130 ms

hero-banner-min.jpg

hero-banner-min.jpg

212 ms

accenturev1.png

accenturev1.png

214 ms

harvard-1.png

harvard-1.png

218 ms

bank-of-america.png

bank-of-america.png

233 ms

kellogg-1.png

kellogg-1.png

260 ms

mit-management-1.png

mit-management-1.png

267 ms

Discover-1.png

Discover-1.png

266 ms

marshall-1.png

marshall-1.png

267 ms

ita-small.png

ita-small.png

271 ms

Play_video_button-min.jpg

Play_video_button-min.jpg

285 ms

home-blurb-process-1-min.png

home-blurb-process-1-min.png

312 ms

process-Arrow-min-e1556231149324.png

process-Arrow-min-e1556231149324.png

318 ms

home-blurb-process-2-min.png

home-blurb-process-2-min.png

320 ms

process-Arrow-min.png

process-Arrow-min.png

319 ms

home-blurb-process-3-min.png

home-blurb-process-3-min.png

323 ms

home-blurb-process-4-min.png

home-blurb-process-4-min.png

339 ms

test-slider-bg-min.jpg

test-slider-bg-min.jpg

366 ms

element_new_f4f2f2-min.png

element_new_f4f2f2-min.png

424 ms

check-min_blue.png

check-min_blue.png

371 ms

check-min.png

check-min.png

372 ms

Lightbulbs_elements-left.png

Lightbulbs_elements-left.png

375 ms

1.png

1.png

530 ms

2.png

2.png

531 ms

3.png

3.png

487 ms

4.png

4.png

488 ms

forbes.png

forbes.png

429 ms

Geek_Wire.png

Geek_Wire.png

487 ms

venture-beat.png

venture-beat.png

487 ms

the-seattle.png

the-seattle.png

564 ms

build-inchicago.png

build-inchicago.png

577 ms

Techstars_logo-white.png

Techstars_logo-white.png

577 ms

footer-logo-v12.png

footer-logo-v12.png

577 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4k.woff

67 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

86 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

107 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

107 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

106 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

108 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

107 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

108 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

108 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

108 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

109 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Ew9.woff

109 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Uw9.woff

110 ms

modules.woff

modules.woff

560 ms

modules.woff

modules.woff

600 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVQ.woff

109 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVQ.woff

110 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVQ.woff

111 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVQ.woff

112 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVQ.woff

112 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVQ.woff

112 ms

collectedforms.js

collectedforms.js

137 ms

banner.js

banner.js

137 ms

fb.js

fb.js

85 ms

web-interactives-embed.js

web-interactives-embed.js

134 ms

2882134.js

2882134.js

146 ms

AUUIHOBCGNGKTJFPBAM77Y

AUUIHOBCGNGKTJFPBAM77Y

14 ms

fbevents.js

fbevents.js

23 ms

out

out

7 ms

AO4QZNAMORDHFDV4XBPWZV

AO4QZNAMORDHFDV4XBPWZV

7 ms

out

out

9 ms

out

out

9 ms

out

out

11 ms

out

out

40 ms

out

out

39 ms

out

out

39 ms

out

out

40 ms

out

out

41 ms

out

out

42 ms

out

out

43 ms

out

out

44 ms

sync

sync

145 ms

trigger

trigger

106 ms

pixel

pixel

127 ms

tap.php

tap.php

105 ms

Pug

Pug

103 ms

pixel

pixel

24 ms

rum

rum

38 ms

generic

generic

19 ms

sd

sd

27 ms

in

in

12 ms

bounce

bounce

34 ms

autoptimize_ac9d2b94e05d672cb538c84f835350fe.css

autoptimize_ac9d2b94e05d672cb538c84f835350fe.css

57 ms

generic

generic

9 ms

receive

receive

19 ms

xuid

xuid

19 ms

wstm1qbk

wstm1qbk

34 ms

Accessibility Review

wesolv.com 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.com 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.com 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.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 Wesolv.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

wesolv.com

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: