Tools & Wizards About Us
qimple.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

qimple.com

Log In | App.alongside.com

Page Load Speed

1.8 sec in total

First Response

18 ms

Resources Loaded

921 ms

Page Rendered

817 ms

qimple.com screenshot

About Website

Welcome to qimple.com homepage info - get ready to check Qimple best content for Canada right away, or after learning these important things about qimple.com

Qimple streamlines your hiring process so you can hire the best candidate in less time.

Visit qimple.com

Key Findings

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

Performance Metrics

qimple.com performance score

0

Network Requests Diagram

qimple.com

18 ms

qimple.com

73 ms

www.qimple.com

68 ms

bootstrap.min.css

17 ms

font-awesome.min.css

43 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 55% of them (23 requests) were addressed to the original Qimple.com, 17% (7 requests) were made to Use.typekit.net and 12% (5 requests) were made to Qimple.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (407 ms) relates to the external source Use.typekit.net.

Page Optimization Overview & Recommendations

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

Content Size

930.8 kB

After Optimization

593.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Qimple.com main page is 930.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. 45% of websites need less resources to load. Images take 452.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 15.4 kB

  • Original 20.9 kB
  • After minification 18.2 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 2.7 kB, which is 13% 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 15.4 kB or 73% of the original size.

Image Optimization

-3%

Potential reduce by 12.1 kB

  • Original 452.3 kB
  • After minification 440.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. Qimple images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 174.6 kB

  • Original 292.9 kB
  • After minification 264.4 kB
  • After compression 118.3 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 174.6 kB or 60% of the original size.

CSS Optimization

-82%

Potential reduce by 135.6 kB

  • Original 164.7 kB
  • After minification 164.6 kB
  • After compression 29.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. Qimple.com needs all CSS files to be minified and compressed as it can save up to 135.6 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (25%)

Requests Now

32

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qimple.com

qimple.com

18 ms

qimple.com

qimple.com

73 ms

www.qimple.com

www.qimple.com

68 ms

bootstrap.min.css

bootstrap.min.css

17 ms

font-awesome.min.css

font-awesome.min.css

43 ms

main.min.css

main.min.css

37 ms

modernizr.js

modernizr.js

56 ms

jquery.min.js

jquery.min.js

171 ms

main.min.js

main.min.js

107 ms

pja6qgb.js

pja6qgb.js

407 ms

gtm.js

gtm.js

327 ms

home_hero_v0.jpg

home_hero_v0.jpg

351 ms

sprites-s2e3a750e95.png

sprites-s2e3a750e95.png

73 ms

qimple_black.png

qimple_black.png

72 ms

products_collage_lg.png

products_collage_lg.png

72 ms

partner1_on.jpg

partner1_on.jpg

218 ms

partner2_off.jpg

partner2_off.jpg

71 ms

partner4_off.jpg

partner4_off.jpg

236 ms

bg_footer_new.jpg

bg_footer_new.jpg

234 ms

audiobooks.png

audiobooks.png

234 ms

compilr.png

compilr.png

228 ms

imperial.png

imperial.png

235 ms

property_guys.png

property_guys.png

226 ms

springboard.png

springboard.png

238 ms

therounds.png

therounds.png

238 ms

logo.png

logo.png

240 ms

overview_laptop.jpg

overview_laptop.jpg

290 ms

overview_create.jpg

overview_create.jpg

336 ms

overview_post.jpg

overview_post.jpg

296 ms

overview_hire.jpg

overview_hire.jpg

336 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

31 ms

analytics.js

analytics.js

107 ms

www.qimple.com

www.qimple.com

29 ms

tumPsPlS4Iopq2_bR5K1r06cPhLW0zoHMStG6cDHgvMffFcUgsMZeMJ6Mk6f5Mw.woff

tumPsPlS4Iopq2_bR5K1r06cPhLW0zoHMStG6cDHgvMffFcUgsMZeMJ6Mk6f5Mw.woff

27 ms

Svi_8k6rSUhvysmY8DjoHCfbzdriAtvEj6UO2lRFYHjffF5UgsMZeMJ6Mk6f5MI.woff

Svi_8k6rSUhvysmY8DjoHCfbzdriAtvEj6UO2lRFYHjffF5UgsMZeMJ6Mk6f5MI.woff

57 ms

hO7hIHFy5n0aNsklFakZJayMPLmg2LzC5fVYOptgzZCffFpUgsMZeMJ6Mk6f5Mb.woff

hO7hIHFy5n0aNsklFakZJayMPLmg2LzC5fVYOptgzZCffFpUgsMZeMJ6Mk6f5Mb.woff

98 ms

-8ITIdDY3v55qYcFh7lrROCUXp25sBiBsJWBsH4r-VGffFAUgsMZeMJ6Mk6f5Mj.woff

-8ITIdDY3v55qYcFh7lrROCUXp25sBiBsJWBsH4r-VGffFAUgsMZeMJ6Mk6f5Mj.woff

128 ms

v68PERuCW_mwu2No8We_cv9y54S1XvPruraUueUmpPbffJY1gsMZeMJ6Mk6f5MS.woff

v68PERuCW_mwu2No8We_cv9y54S1XvPruraUueUmpPbffJY1gsMZeMJ6Mk6f5MS.woff

145 ms

collect

collect

39 ms

collect

collect

73 ms

p.gif

p.gif

127 ms

ga-audiences

ga-audiences

39 ms

SEO Factors

qimple.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 Qimple.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 Qimple.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

qimple.com

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