Tools & Wizards About Us
123count.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

123count.com

123Count | Website Analytics | Full Visitor Details | Free Stats

Page Load Speed

1.4 sec in total

First Response

80 ms

Resources Loaded

1 sec

Page Rendered

251 ms

123count.com screenshot

About Website

Visit 123count.com now to see the best up-to-date 123Count content for Canada and also check out these interesting facts you probably never knew about 123count.com

Track individual visitors using your website in real-time. Understand & grow your traffic with free, live analytics. Add to your site in minutes!

Visit 123count.com

Key Findings

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

Performance Metrics

123count.com performance score

0

Network Requests Diagram

123count.com

80 ms

www.123count.com

87 ms

jquery.min.js

37 ms

ajax.js

26 ms

custom_scripts.js

64 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 38% of them (20 requests) were addressed to the original 123count.com, 34% (18 requests) were made to Web-stat.com and 8% (4 requests) were made to C555142.r42.cf2.rackcdn.com. The less responsive or slowest element that took the longest time to load (397 ms) relates to the external source Web-stat.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.3 kB (48%)

Content Size

520.8 kB

After Optimization

269.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 123count.com main page is 520.8 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. 40% of websites need less resources to load. Javascripts take 241.1 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 9.6 kB

  • Original 14.2 kB
  • After minification 13.8 kB
  • After compression 4.6 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 9.6 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 45 B

  • Original 164.3 kB
  • After minification 164.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. 123Count images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 152.1 kB

  • Original 241.1 kB
  • After minification 220.8 kB
  • After compression 89.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 152.1 kB or 63% of the original size.

CSS Optimization

-88%

Potential reduce by 89.5 kB

  • Original 101.2 kB
  • After minification 55.2 kB
  • After compression 11.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. 123count.com needs all CSS files to be minified and compressed as it can save up to 89.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

123count.com

123count.com

80 ms

www.123count.com

www.123count.com

87 ms

jquery.min.js

jquery.min.js

37 ms

ajax.js

ajax.js

26 ms

custom_scripts.js

custom_scripts.js

64 ms

css

css

36 ms

css_screen_1.pl

css_screen_1.pl

57 ms

sweetalert.min.js

sweetalert.min.js

69 ms

sweetalert.min.css

sweetalert.min.css

76 ms

corner_tl.gif

corner_tl.gif

24 ms

tab1_img2.gif

tab1_img2.gif

24 ms

tab2_img2.gif

tab2_img2.gif

24 ms

tab3_img2.gif

tab3_img2.gif

44 ms

logo_web.png

logo_web.png

87 ms

menu_bars.png

menu_bars.png

120 ms

log6_2.js

log6_2.js

70 ms

demo_streaming.pl

demo_streaming.pl

397 ms

arrow_left3.png

arrow_left3.png

30 ms

arrow_right3.png

arrow_right3.png

30 ms

shadow2.png

shadow2.png

32 ms

sample_graph1.png

sample_graph1.png

64 ms

sample_graph2.png

sample_graph2.png

70 ms

sample_graph3.png

sample_graph3.png

92 ms

divider_wide_pattern.png

divider_wide_pattern.png

53 ms

bullet_purple.png

bullet_purple.png

50 ms

arrow_grey_right.png

arrow_grey_right.png

55 ms

bubble_point.png

bubble_point.png

74 ms

corner_tl.gif

corner_tl.gif

69 ms

tab1_img2.gif

tab1_img2.gif

316 ms

tab2_img2.gif

tab2_img2.gif

211 ms

tab3_img2.gif

tab3_img2.gif

112 ms

count6.pl

count6.pl

39 ms

main_print.css

main_print.css

23 ms

y7lebkjgREBJK96VQi37Zl02b4v3fUxqf9CZJ1qUoIA.ttf

y7lebkjgREBJK96VQi37Zl02b4v3fUxqf9CZJ1qUoIA.ttf

10 ms

dazS1PrQQuCxC3iOAJFEJfqEJM-AK1nFUafhVdytxUY.ttf

dazS1PrQQuCxC3iOAJFEJfqEJM-AK1nFUafhVdytxUY.ttf

29 ms

MEz38VLIFL-t46JUtkIEgPPf2A2FX0VDSaBsAF1m6CU.ttf

MEz38VLIFL-t46JUtkIEgPPf2A2FX0VDSaBsAF1m6CU.ttf

28 ms

custom_scripts_min.js

custom_scripts_min.js

115 ms

ajax_getNewVisitors_demo.min.js

ajax_getNewVisitors_demo.min.js

132 ms

ajax_getNewPaths_demo.min.js

ajax_getNewPaths_demo.min.js

115 ms

overlib.js

overlib.js

14 ms

jquery.min.js

jquery.min.js

117 ms

anirows.js

anirows.js

19 ms

hk.gif

hk.gif

175 ms

0.png

0.png

177 ms

os_windows.gif

os_windows.gif

133 ms

browsers_chrome.gif

browsers_chrome.gif

136 ms

bar_element_blue.gif

bar_element_blue.gif

137 ms

main.css

main.css

124 ms

css_screen_1.css

css_screen_1.css

189 ms

Font_Roboto_Slab.css

Font_Roboto_Slab.css

245 ms

y7lebkjgREBJK96VQi37ZrrIa-7acMAeDBVuclsi6Gc.woff

y7lebkjgREBJK96VQi37ZrrIa-7acMAeDBVuclsi6Gc.woff

86 ms

dazS1PrQQuCxC3iOAJFEJfR_54zmj3SbGZQh3vCOwvY.woff

dazS1PrQQuCxC3iOAJFEJfR_54zmj3SbGZQh3vCOwvY.woff

131 ms

MEz38VLIFL-t46JUtkIEgKwsIWd7evfOerjO4J_CQWU.woff

MEz38VLIFL-t46JUtkIEgKwsIWd7evfOerjO4J_CQWU.woff

5 ms

SEO Factors

123count.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 123count.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that 123count.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

123count.com

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