Tools & Wizards About Us
source2.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

source2.com

Source2 - Recruiting and Retention of Frontline Employees

Page Load Speed

1.9 sec in total

First Response

164 ms

Resources Loaded

1.2 sec

Page Rendered

510 ms

source2.com screenshot

About Website

Click here to check amazing Source2 content for United States. Otherwise, check out these important facts you probably never knew about source2.com

RECRUIT & RETAIN THE BEST FRONTLINE TALENT. Our flexible, personal, modern approach ensures meaningful results and an unforgettable service experience.

Visit source2.com

Key Findings

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

Performance Metrics

source2.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.006

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

source2.com

164 ms

www.source2.com

175 ms

jquery-1.7.1.js

30 ms

main.min.css

203 ms

theme-overrides.min.css

234 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 55% of them (26 requests) were addressed to the original Source2.com, 4% (2 requests) were made to Static.hsappstatic.net and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (621 ms) belongs to the original domain Source2.com.

Page Optimization Overview & Recommendations

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

Content Size

756.2 kB

After Optimization

678.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Source2.com main page is 756.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. Images take 566.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 68.0 kB

  • Original 79.9 kB
  • After minification 75.4 kB
  • After compression 11.9 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 68.0 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 1.3 kB

  • Original 566.9 kB
  • After minification 565.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. Source2 images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 6.2 kB

  • Original 98.0 kB
  • After minification 98.0 kB
  • After compression 91.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

-16%

Potential reduce by 1.8 kB

  • Original 11.4 kB
  • After minification 11.4 kB
  • After compression 9.5 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. Source2.com needs all CSS files to be minified and compressed as it can save up to 1.8 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (66%)

Requests Now

41

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

source2.com

source2.com

164 ms

www.source2.com

www.source2.com

175 ms

jquery-1.7.1.js

jquery-1.7.1.js

30 ms

main.min.css

main.min.css

203 ms

theme-overrides.min.css

theme-overrides.min.css

234 ms

css

css

45 ms

module_29460748196_menu-section.min.css

module_29460748196_menu-section.min.css

229 ms

module_29636927809_Spoke_RSS_Module.min.css

module_29636927809_Spoke_RSS_Module.min.css

204 ms

module_29450920862_social-follow.min.css

module_29450920862_social-follow.min.css

245 ms

223618.js

223618.js

65 ms

embed.js

embed.js

42 ms

main.min.js

main.min.js

229 ms

project.js

project.js

238 ms

module_29460748196_menu-section.min.js

module_29460748196_menu-section.min.js

423 ms

loader.js

loader.js

54 ms

1955602.js

1955602.js

325 ms

index.js

index.js

291 ms

CompanyMain.min.js

CompanyMain.min.js

621 ms

gtm.js

gtm.js

88 ms

badge-clear.gif

badge-clear.gif

158 ms

Source2_NoTag_Logo_(PRINT%2060px)2757_7689.png

Source2_NoTag_Logo_(PRINT%2060px)2757_7689.png

65 ms

Source2-2022HeroImage-1600x705-April2022.jpg

Source2-2022HeroImage-1600x705-April2022.jpg

155 ms

Homepage_Recruitment-1.jpg

Homepage_Recruitment-1.jpg

64 ms

Professional-CompCandidate-1650x543.jpg

Professional-CompCandidate-1650x543.jpg

152 ms

Homepage_Retention-1.jpg

Homepage_Retention-1.jpg

154 ms

Homepage_Technology-3.jpg

Homepage_Technology-3.jpg

153 ms

Source2-BobByrne-Video-1024x%20512px.jpg

Source2-BobByrne-Video-1024x%20512px.jpg

158 ms

Source2-WFHBlog-Header-1024x512px.jpg

Source2-WFHBlog-Header-1024x512px.jpg

160 ms

Source2-CaseStudy-FoodService-1024x512px.jpg

Source2-CaseStudy-FoodService-1024x512px.jpg

159 ms

regular.woff

regular.woff

137 ms

600.woff

600.woff

168 ms

700.woff

700.woff

177 ms

js

js

89 ms

2fd4ade2849c5277.min.js

2fd4ade2849c5277.min.js

198 ms

1955602.js

1955602.js

276 ms

1955602.js

1955602.js

333 ms

leadflows.js

leadflows.js

283 ms

fb.js

fb.js

275 ms

insight.min.js

insight.min.js

129 ms

sync

sync

115 ms

insight_tag_errors.gif

insight_tag_errors.gif

124 ms

sync

sync

40 ms

tap.php

tap.php

47 ms

ip.json

ip.json

83 ms

rum

rum

25 ms

log

log

51 ms

li_sync

li_sync

52 ms

Accessibility Review

source2.com accessibility score

95

Accessibility Issues

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

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

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

source2.com SEO score

86

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

source2.com

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