Tools & Wizards About Us
splithistory.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

splithistory.com

Split History

Page Load Speed

2.8 sec in total

First Response

96 ms

Resources Loaded

2.2 sec

Page Rendered

556 ms

splithistory.com screenshot

About Website

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

A split history directory for stocks that have split their shares.

Visit splithistory.com

Key Findings

We analyzed Splithistory.com page load time and found that the first response time was 96 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

splithistory.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

30/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value1,960 ms

8/100

30%

CLS (Cumulative Layout Shift)

Value0.334

34/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

splithistory.com

96 ms

www.splithistory.com

1337 ms

swfobject.js

91 ms

jquery-3.2.1.min.js

13 ms

tbs.js

103 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 22% of them (20 requests) were addressed to the original Splithistory.com, 27% (25 requests) were made to Marketbeat.com and 15% (14 requests) were made to Stocksplithistory.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Splithistory.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 518.0 kB (34%)

Content Size

1.5 MB

After Optimization

984.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Splithistory.com main page is 1.5 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. 45% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 42.5 kB

  • Original 54.0 kB
  • After minification 53.0 kB
  • After compression 11.5 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 42.5 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 12.9 kB

  • Original 447.9 kB
  • After minification 435.0 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. Split History images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 462.5 kB

  • Original 1.0 MB
  • After minification 999.7 kB
  • After compression 537.5 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 462.5 kB or 46% of the original size.

Requests Breakdown

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

Requests Now

87

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

splithistory.com

splithistory.com

96 ms

www.splithistory.com

www.splithistory.com

1337 ms

swfobject.js

swfobject.js

91 ms

jquery-3.2.1.min.js

jquery-3.2.1.min.js

13 ms

tbs.js

tbs.js

103 ms

jwplayer.js

jwplayer.js

110 ms

gpt.js

gpt.js

52 ms

pagebkg.gif

pagebkg.gif

237 ms

tpixel.gif

tpixel.gif

357 ms

split-history-logo.png

split-history-logo.png

377 ms

vicon.gif

vicon.gif

387 ms

sandp.png

sandp.png

358 ms

consumer.png

consumer.png

356 ms

energy.png

energy.png

357 ms

financials.png

financials.png

459 ms

like.php

like.php

226 ms

favicon.gif

favicon.gif

321 ms

HeaderAdPartnerSites.ashx

HeaderAdPartnerSites.ashx

89 ms

mnvt1.gif

mnvt1.gif

23 ms

canadastockfavicon.gif

canadastockfavicon.gif

60 ms

ceffavicon.gif

ceffavicon.gif

82 ms

dividendfavicon.gif

dividendfavicon.gif

79 ms

energystockfavicon.gif

energystockfavicon.gif

79 ms

etffavicon.gif

etffavicon.gif

80 ms

holdingsfavicon.gif

holdingsfavicon.gif

79 ms

metalsfavicon.gif

metalsfavicon.gif

80 ms

opfavicon.gif

opfavicon.gif

140 ms

psfavicon.gif

psfavicon.gif

141 ms

tcfavicon.gif

tcfavicon.gif

207 ms

olifavicon.gif

olifavicon.gif

209 ms

vffavicon.gif

vffavicon.gif

141 ms

buttonbkg.gif

buttonbkg.gif

380 ms

tabbkg.gif

tabbkg.gif

393 ms

vast.js

vast.js

48 ms

jwpsrv.js

jwpsrv.js

53 ms

SidebarAdPartnerSites.ashx

SidebarAdPartnerSites.ashx

59 ms

pubads_impl.js

pubads_impl.js

35 ms

336x280AdPartnerSites.ashx

336x280AdPartnerSites.ashx

141 ms

MarkGloss_Splits.jpg

MarkGloss_Splits.jpg

11 ms

logo.png

logo.png

3 ms

healthcare.png

healthcare.png

335 ms

industrials.png

industrials.png

344 ms

materials.png

materials.png

413 ms

services.png

services.png

356 ms

technology.png

technology.png

373 ms

utilities.png

utilities.png

387 ms

misc.png

misc.png

389 ms

css2

css2

136 ms

MoreOnMarketBeatPartnerSites.aspx

MoreOnMarketBeatPartnerSites.aspx

123 ms

contextfeed.js

contextfeed.js

151 ms

js

js

140 ms

exitpop.js

exitpop.js

367 ms

ads

ads

484 ms

container.html

container.html

108 ms

navltsunami01.png

navltsunami01.png

101 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

88 ms

thumb_2061push_capital-5043172_640.jpg

thumb_2061push_capital-5043172_640.jpg

86 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

88 ms

thumb_2070push_AI-9.jpg

thumb_2070push_AI-9.jpg

88 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

102 ms

thumb_2080push_AI-9.jpg

thumb_2080push_AI-9.jpg

240 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

137 ms

thumb_2047push_yacht-4292334_640.jpg

thumb_2047push_yacht-4292334_640.jpg

115 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

155 ms

thumb_2044push_money_02_720x480.jpg

thumb_2044push_money_02_720x480.jpg

115 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

155 ms

thumb_2061push_Picture1.png

thumb_2061push_Picture1.png

136 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

174 ms

20240417142941_20240417tmi01.png

20240417142941_20240417tmi01.png

166 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

176 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

201 ms

thumb_2050push_Warren-Buffett_02_720x480.jpg

thumb_2050push_Warren-Buffett_02_720x480.jpg

172 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

222 ms

thumb_2052push_coal.jpg

thumb_2052push_coal.jpg

193 ms

TriggeredCampaignPixel.ashx

TriggeredCampaignPixel.ashx

225 ms

med_generic_stock_0673741300.jpg

med_generic_stock_0673741300.jpg

192 ms

vwgziwe0FNr.js

vwgziwe0FNr.js

98 ms

FEppCFCt76d.png

FEppCFCt76d.png

107 ms

platform.js

platform.js

74 ms

quant.js

quant.js

65 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

25 ms

fastbutton

fastbutton

35 ms

postmessageRelay

postmessageRelay

67 ms

developers.google.com

developers.google.com

416 ms

3636781319-postmessagerelay.js

3636781319-postmessagerelay.js

18 ms

rpc:shindig_random.js

rpc:shindig_random.js

13 ms

beacon.js

beacon.js

19 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

5 ms

abg_lite.js

abg_lite.js

15 ms

ufs_web_display.js

ufs_web_display.js

25 ms

Accessibility Review

splithistory.com accessibility score

80

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

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

Best Practices

splithistory.com best practices score

50

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

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

splithistory.com SEO score

69

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

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 Splithistory.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 Splithistory.com 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

splithistory.com

Open Graph description is not detected on the main page of Split History. 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: