Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

splitbar.com

SplitBar XT - Professional split bars and form splitter ActiveX

Page Load Speed

558 ms in total

First Response

169 ms

Resources Loaded

304 ms

Page Rendered

85 ms

About Website

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

SplitBar XT activeX easily adds hotizontal and vertical split bars and auto resize functions. Build simple yet powerful hosting, splitting and resizing multi panes applications without code. Individua...

Visit splitbar.com

Key Findings

We analyzed Splitbar.com page load time and found that the first response time was 169 ms and then it took 389 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

splitbar.com performance score

0

Network Requests Diagram

splitbar.com

169 ms

cell_bkg.gif

77 ms

logo.gif

110 ms

icons.gif

117 ms

overview-over.gif

83 ms

Our browser made a total of 20 requests to load all elements on the main page. We found that all of those requests were addressed to Splitbar.com and no external sources were called. The less responsive or slowest element that took the longest time to load (169 ms) belongs to the original domain Splitbar.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 8.2 kB (78%)

Content Size

10.6 kB

After Optimization

2.4 kB

In fact, the total size of Splitbar.com main page is 10.6 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 10.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 8.2 kB

  • Original 10.6 kB
  • After minification 9.0 kB
  • After compression 2.4 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 1.6 kB, which is 15% 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 8.2 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (63%)

Requests Now

19

After Optimization

7

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

SEO Factors

splitbar.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Splitbar.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Splitbar.com main page’s claimed encoding is windows-1252. 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

Open Graph description is not detected on the main page of Split Bar. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: