Tools & Wizards About Us
position1.ca screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

position1.ca

Position1.ca | Spécialistes en positionnement Google | Montréal, Québec, Canada

Page Load Speed

929 ms in total

First Response

296 ms

Resources Loaded

462 ms

Page Rendered

171 ms

position1.ca screenshot

About Website

Welcome to position1.ca homepage info - get ready to check Position1 best content right away, or after learning these important things about position1.ca

Spécialistes du positionnement Google depuis plus de 10 ans, l'équipe de Position 1 vous offre des services web adaptés à votre budget et à vos objectifs.

Visit position1.ca

Key Findings

We analyzed Position1.ca page load time and found that the first response time was 296 ms and then it took 633 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

position1.ca performance score

0

Network Requests Diagram

position1.ca

296 ms

style.css

26 ms

styles.css

28 ms

jquery-ui-1.8.18.custom.css

42 ms

jquery.fancybox.css

29 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 97% of them (57 requests) were addressed to the original Position1.ca, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (296 ms) belongs to the original domain Position1.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 364.9 kB (36%)

Content Size

1.0 MB

After Optimization

650.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Position1.ca main page is 1.0 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. Images take 505.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 18.7 kB

  • Original 23.4 kB
  • After minification 20.8 kB
  • After compression 4.8 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 2.7 kB, which is 11% 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 18.7 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 9.1 kB

  • Original 505.7 kB
  • After minification 496.6 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. Position1 images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 283.3 kB

  • Original 421.5 kB
  • After minification 393.8 kB
  • After compression 138.2 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 283.3 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 53.8 kB

  • Original 65.1 kB
  • After minification 48.8 kB
  • After compression 11.2 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. Position1.ca needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

position1.ca

position1.ca

296 ms

style.css

style.css

26 ms

styles.css

styles.css

28 ms

jquery-ui-1.8.18.custom.css

jquery-ui-1.8.18.custom.css

42 ms

jquery.fancybox.css

jquery.fancybox.css

29 ms

jquery.fancybox-thumbs.css

jquery.fancybox-thumbs.css

30 ms

jquery.fancybox-buttons.css

jquery.fancybox-buttons.css

30 ms

jquery.js

jquery.js

52 ms

jquery-migrate.min.js

jquery-migrate.min.js

43 ms

swfobject.js

swfobject.js

43 ms

jquery.main.js

jquery.main.js

33 ms

jquery.cycle.all.js

jquery.cycle.all.js

61 ms

jquery.validate.min.js

jquery.validate.min.js

58 ms

custom.js

custom.js

59 ms

jquery.form.min.js

jquery.form.min.js

60 ms

scripts.js

scripts.js

58 ms

jquery.ui.core.min.js

jquery.ui.core.min.js

59 ms

jquery.ui.widget.min.js

jquery.ui.widget.min.js

60 ms

jquery.ui.mouse.min.js

jquery.ui.mouse.min.js

66 ms

jquery.ui.resizable.min.js

jquery.ui.resizable.min.js

68 ms

jquery.ui.draggable.min.js

jquery.ui.draggable.min.js

69 ms

jquery.ui.button.min.js

jquery.ui.button.min.js

99 ms

jquery.ui.position.min.js

jquery.ui.position.min.js

99 ms

jquery.ui.dialog.min.js

jquery.ui.dialog.min.js

100 ms

jquery.ui.sortable.min.js

jquery.ui.sortable.min.js

103 ms

jquery.ui.tabs.min.js

jquery.ui.tabs.min.js

101 ms

jquery.ui.selectable.min.js

jquery.ui.selectable.min.js

102 ms

jquery.ui.accordion.min.js

jquery.ui.accordion.min.js

102 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

102 ms

jquery.url.js

jquery.url.js

106 ms

jquery.md5.js

jquery.md5.js

106 ms

jquery.ui.datepicker.min.js

jquery.ui.datepicker.min.js

106 ms

jquery.alert.js

jquery.alert.js

108 ms

ga.js

ga.js

18 ms

bg-header.gif

bg-header.gif

77 ms

bg-header2.gif

bg-header2.gif

78 ms

Mail.png

Mail.png

76 ms

Facebook.png

Facebook.png

76 ms

Twitter.png

Twitter.png

77 ms

linkedin.png

linkedin.png

78 ms

google_plus.png

google_plus.png

78 ms

press-me-button-small.png

press-me-button-small.png

79 ms

slogan.jpg

slogan.jpg

79 ms

logo.png

logo.png

79 ms

bg-nav-hover.gif

bg-nav-hover.gif

80 ms

slide1.png

slide1.png

80 ms

slide2.png

slide2.png

87 ms

slide3.png

slide3.png

103 ms

google-search.jpg

google-search.jpg

87 ms

positioning-google.jpg

positioning-google.jpg

88 ms

google-maps.jpg

google-maps.jpg

79 ms

bg-info-area-b.png

bg-info-area-b.png

82 ms

bg-sign-today.png

bg-sign-today.png

89 ms

bg-signup.png

bg-signup.png

89 ms

bg-footer.gif

bg-footer.gif

93 ms

bullet-list.gif

bullet-list.gif

94 ms

__utm.gif

__utm.gif

36 ms

ui-bg_highlight-hard_100_eeeeee_1x100.png

ui-bg_highlight-hard_100_eeeeee_1x100.png

31 ms

helveticaneue-boldcond-webfont.woff

helveticaneue-boldcond-webfont.woff

32 ms

SEO Factors

position1.ca SEO score

0

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Position1.ca can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it does not match the claimed English language. Our system also found out that Position1.ca 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

position1.ca

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