Tools & Wizards About Us
splitfee.org screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

splitfee.org

SplitFee JobBoard - Recruitment and Recruiter Split Fee Jobs

Page Load Speed

4 sec in total

First Response

329 ms

Resources Loaded

3.3 sec

Page Rendered

390 ms

splitfee.org screenshot

About Website

Welcome to splitfee.org homepage info - get ready to check Split Fee best content for Kenya right away, or after learning these important things about splitfee.org

Connecting recruiters to new jobs. Biggest agency marketplace with over 1000 agencies. If you're not on the SplitFee Platform you're missing out!

Visit splitfee.org

Key Findings

We analyzed Splitfee.org page load time and found that the first response time was 329 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

splitfee.org performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value2,700 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.068

96/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

splitfee.org

329 ms

splitfee.org

590 ms

1613380674fdd658518ab5af87432364d07d77cce4.css

397 ms

161340447594cdfc2d2d7131608f450d5f5b9923e6.css

240 ms

1612436475aed32c81c2315aaaac07be93262109ab.js

960 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 93% of them (26 requests) were addressed to the original Splitfee.org, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Splitfee.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 212.6 kB (61%)

Content Size

348.7 kB

After Optimization

136.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Splitfee.org main page is 348.7 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. 25% of websites need less resources to load. CSS take 178.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 33.7 kB

  • Original 40.7 kB
  • After minification 34.3 kB
  • After compression 7.0 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. This page needs HTML code to be minified as it can gain 6.5 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.7 kB or 83% of the original size.

Image Optimization

-15%

Potential reduce by 12.6 kB

  • Original 82.3 kB
  • After minification 69.7 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. Obviously, Split Fee needs image optimization as it can save up to 12.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-42%

Potential reduce by 19.6 kB

  • Original 47.3 kB
  • After minification 47.2 kB
  • After compression 27.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 19.6 kB or 42% of the original size.

CSS Optimization

-82%

Potential reduce by 146.6 kB

  • Original 178.3 kB
  • After minification 177.6 kB
  • After compression 31.7 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. Splitfee.org needs all CSS files to be minified and compressed as it can save up to 146.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (14%)

Requests Now

22

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

splitfee.org

splitfee.org

329 ms

splitfee.org

splitfee.org

590 ms

1613380674fdd658518ab5af87432364d07d77cce4.css

1613380674fdd658518ab5af87432364d07d77cce4.css

397 ms

161340447594cdfc2d2d7131608f450d5f5b9923e6.css

161340447594cdfc2d2d7131608f450d5f5b9923e6.css

240 ms

1612436475aed32c81c2315aaaac07be93262109ab.js

1612436475aed32c81c2315aaaac07be93262109ab.js

960 ms

1612181508eaba71696c2a1870d4a535c9e165df68.js

1612181508eaba71696c2a1870d4a535c9e165df68.js

247 ms

bootstrap.validator.min.js

bootstrap.validator.min.js

244 ms

header.png

header.png

86 ms

splitfee-logo-white.png

splitfee-logo-white.png

86 ms

slider-1.png

slider-1.png

167 ms

ajax-loader.gif

ajax-loader.gif

86 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

119 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

194 ms

linkedin-footer.png

linkedin-footer.png

162 ms

facebook-footer.png

facebook-footer.png

159 ms

twitter-footer.png

twitter-footer.png

158 ms

rss-footer.png

rss-footer.png

158 ms

go.png

go.png

157 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

217 ms

analytics.js

analytics.js

156 ms

countries

countries

1122 ms

regions

regions

1054 ms

careers

careers

1086 ms

educations

educations

1084 ms

sectors

sectors

1034 ms

job

job

1154 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1174 ms

collect

collect

36 ms

Accessibility Review

splitfee.org accessibility score

81

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.

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

splitfee.org 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

splitfee.org SEO score

62

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Splitfee.org 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 Splitfee.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

splitfee.org

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