Tools & Wizards About Us
trueslant.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

trueslant.com

True/Slant

Page Load Speed

1.2 sec in total

First Response

138 ms

Resources Loaded

738 ms

Page Rendered

332 ms

trueslant.com screenshot

About Website

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

Visit trueslant.com

Key Findings

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

Performance Metrics

trueslant.com performance score

0

Network Requests Diagram

trueslant.com

138 ms

trueslant-tsone.css

247 ms

roger.css

54 ms

jquery.js

172 ms

jquery.selso-1.0.1.js

52 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 83% of them (52 requests) were addressed to the original Trueslant.com, 5% (3 requests) were made to Facebook.com and 5% (3 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (316 ms) belongs to the original domain Trueslant.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 292.3 kB (72%)

Content Size

407.0 kB

After Optimization

114.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Trueslant.com main page is 407.0 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 176.9 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 43.8 kB

  • Original 56.3 kB
  • After minification 52.6 kB
  • After compression 12.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 43.8 kB or 78% of the original size.

Image Optimization

-4%

Potential reduce by 1.3 kB

  • Original 33.5 kB
  • After minification 32.2 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. True Slant images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 96.3 kB

  • Original 140.3 kB
  • After minification 136.4 kB
  • After compression 44.0 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 96.3 kB or 69% of the original size.

CSS Optimization

-85%

Potential reduce by 150.8 kB

  • Original 176.9 kB
  • After minification 150.1 kB
  • After compression 26.1 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. Trueslant.com needs all CSS files to be minified and compressed as it can save up to 150.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (49%)

Requests Now

57

After Optimization

29

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

trueslant.com

trueslant.com

138 ms

trueslant-tsone.css

trueslant-tsone.css

247 ms

roger.css

roger.css

54 ms

jquery.js

jquery.js

172 ms

jquery.selso-1.0.1.js

jquery.selso-1.0.1.js

52 ms

ppimu.js

ppimu.js

82 ms

jquery.quickpaginate.js

jquery.quickpaginate.js

80 ms

jquery.cookie.js

jquery.cookie.js

59 ms

jquery.overlay-1.0.1.js

jquery.overlay-1.0.1.js

101 ms

jquery.expose-1.0.0.js

jquery.expose-1.0.0.js

109 ms

topic.js

topic.js

129 ms

follow.js

follow.js

153 ms

clip.js

clip.js

152 ms

recommend.js

recommend.js

156 ms

ui.core.js

ui.core.js

197 ms

ui.tabs.js

ui.tabs.js

308 ms

alluser.js

alluser.js

307 ms

jquery.scrollable-1.0.1.js

jquery.scrollable-1.0.1.js

307 ms

callout.js

callout.js

308 ms

FeatureLoader.js.php

FeatureLoader.js.php

125 ms

fbconnect.js

fbconnect.js

309 ms

quant.js

quant.js

11 ms

ts_global_nav_sprite.gif

ts_global_nav_sprite.gif

77 ms

ts_main_sprite.gif

ts_main_sprite.gif

211 ms

ts_logos_sprite.gif

ts_logos_sprite.gif

108 ms

h-line-middle.gif

h-line-middle.gif

76 ms

michaelroston_40.jpg

michaelroston_40.jpg

77 ms

dvorkin_40.jpg

dvorkin_40.jpg

77 ms

andreaitis_40.jpg

andreaitis_40.jpg

107 ms

erikkain_40.jpg

erikkain_40.jpg

111 ms

scotthpayne_40.jpg

scotthpayne_40.jpg

111 ms

4511330595_87d2b5562b_m1.jpg

4511330595_87d2b5562b_m1.jpg

208 ms

oshagraydavidson_40.jpg

oshagraydavidson_40.jpg

204 ms

370208387_77dda03a67_m.jpg

370208387_77dda03a67_m.jpg

216 ms

franmorelandjohns_40.jpg

franmorelandjohns_40.jpg

210 ms

shevchuk.jpg

shevchuk.jpg

211 ms

juliaioffe_40.jpg

juliaioffe_40.jpg

211 ms

ts_video_arrows_sprite.png

ts_video_arrows_sprite.png

213 ms

matthewnewton_40.jpg

matthewnewton_40.jpg

214 ms

300px-Anne_Rice.jpg

300px-Anne_Rice.jpg

219 ms

icon-doublequote.png

icon-doublequote.png

222 ms

michaelhumphrey_40.jpg

michaelhumphrey_40.jpg

240 ms

Amir_Khan_2007_140x190.jpg

Amir_Khan_2007_140x190.jpg

250 ms

bencohen_40.jpg

bencohen_40.jpg

243 ms

bg_inside_left_middle.gif

bg_inside_left_middle.gif

244 ms

kashmirhill_40.jpg

kashmirhill_40.jpg

266 ms

fruzsinaeordogh_40.jpg

fruzsinaeordogh_40.jpg

271 ms

scottbowen_40.jpg

scottbowen_40.jpg

279 ms

suefrause_40.jpg

suefrause_40.jpg

293 ms

marceloballve_40.jpg

marceloballve_40.jpg

293 ms

scottyoung_40.jpg

scottyoung_40.jpg

300 ms

ts_live_streams_plural.png

ts_live_streams_plural.png

316 ms

bg-bottomline.png

bg-bottomline.png

281 ms

42 ms

ga.js

ga.js

37 ms

102 ms

101 ms

xd_arbiter.php

xd_arbiter.php

133 ms

xd_arbiter.php

xd_arbiter.php

232 ms

pixel;r=1161899878;a=p-42WIex_FAM6DU;fpan=1;fpa=P0-287687779-1458130855063;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458130855062;tzo=-180;ref=;url=http%3A%2F%2Ftrueslant.com%2F;ogl=

pixel;r=1161899878;a=p-42WIex_FAM6DU;fpan=1;fpa=P0-287687779-1458130855063;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1458130855062;tzo=-180;ref=;url=http%3A%2F%2Ftrueslant.com%2F;ogl=

59 ms

__utm.gif

__utm.gif

24 ms

streams-arrow.gif

streams-arrow.gif

134 ms

xd_arbiter.php

xd_arbiter.php

98 ms

SEO Factors

trueslant.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Trueslant.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 Trueslant.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

trueslant.com

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