Tools & Wizards About Us
janzz.ch screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

janzz.ch

JANZZ.jobs

Page Load Speed

4.3 sec in total

First Response

312 ms

Resources Loaded

3.9 sec

Page Rendered

141 ms

janzz.ch screenshot

About Website

Visit janzz.ch now to see the best up-to-date JANZZ content and also check out these interesting facts you probably never knew about janzz.ch

All the Skills of the World. On a single platform. With just a few clicks, JANZZ uniquely matches people, businesses, jobs and projects with perfectly selected skills, expertise and experience - anony...

Visit janzz.ch

Key Findings

We analyzed Janzz.ch page load time and found that the first response time was 312 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

janzz.ch performance score

0

Network Requests Diagram

janzz.ch

312 ms

www.janzz.jobs

906 ms

janzz.css

612 ms

form_styles.css

637 ms

jquery-ui-1.8.16.custom.css

651 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Janzz.ch, 63% (43 requests) were made to Media.janzz.jobs and 12% (8 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Media.janzz.jobs.

Page Optimization Overview & Recommendations

Page size can be reduced by 825.2 kB (47%)

Content Size

1.7 MB

After Optimization

915.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Janzz.ch main page is 1.7 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 786.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 62.7 kB

  • Original 78.0 kB
  • After minification 74.4 kB
  • After compression 15.3 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 62.7 kB or 80% of the original size.

Image Optimization

-16%

Potential reduce by 128.9 kB

  • Original 786.9 kB
  • After minification 658.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. Obviously, JANZZ needs image optimization as it can save up to 128.9 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-71%

Potential reduce by 542.7 kB

  • Original 766.7 kB
  • After minification 764.5 kB
  • After compression 224.1 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 542.7 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 91.0 kB

  • Original 109.3 kB
  • After minification 86.8 kB
  • After compression 18.3 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. Janzz.ch needs all CSS files to be minified and compressed as it can save up to 91.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (48%)

Requests Now

66

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

janzz.ch

janzz.ch

312 ms

www.janzz.jobs

www.janzz.jobs

906 ms

janzz.css

janzz.css

612 ms

form_styles.css

form_styles.css

637 ms

jquery-ui-1.8.16.custom.css

jquery-ui-1.8.16.custom.css

651 ms

jquery.multiselect.css

jquery.multiselect.css

670 ms

jquery-ui-changes.css

jquery-ui-changes.css

677 ms

plusone.js

plusone.js

62 ms

janzz_0_213.js

janzz_0_213.js

1398 ms

jquery.cycle.lite.1.0.min.js

jquery.cycle.lite.1.0.min.js

736 ms

registration.js

registration.js

752 ms

landingpage.js

landingpage.js

773 ms

quicksearch.js

quicksearch.js

783 ms

janzz_1_213.js

janzz_1_213.js

783 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

6 ms

ga.js

ga.js

208 ms

tracking.js

tracking.js

302 ms

315 ms

gplus-64.png

gplus-64.png

232 ms

navigation_line.gif

navigation_line.gif

186 ms

eurostars_logo.png

eurostars_logo.png

184 ms

janzz_logo1_en.png

janzz_logo1_en.png

234 ms

regbannergradient.png

regbannergradient.png

184 ms

landing_rot_en.png

landing_rot_en.png

234 ms

landing_vid_en.png

landing_vid_en.png

184 ms

janzzWEB_01.jpg

janzzWEB_01.jpg

597 ms

janzzWEB_02.jpg

janzzWEB_02.jpg

616 ms

janzzWEB_03.jpg

janzzWEB_03.jpg

503 ms

janzzWEB_04.jpg

janzzWEB_04.jpg

663 ms

janzzWEB_05.jpg

janzzWEB_05.jpg

529 ms

janzzWEB_06.jpg

janzzWEB_06.jpg

871 ms

janzzWEB_07.jpg

janzzWEB_07.jpg

725 ms

janzzWEB_08.jpg

janzzWEB_08.jpg

825 ms

janzzWEB_09.jpg

janzzWEB_09.jpg

901 ms

graybg1.png

graybg1.png

722 ms

janzzfinder_2.png

janzzfinder_2.png

758 ms

info.png

info.png

830 ms

buttons_bg.gif

buttons_bg.gif

832 ms

xing_16.png

xing_16.png

856 ms

linkedin_16.png

linkedin_16.png

925 ms

bgsponsor.png

bgsponsor.png

938 ms

graybg2.png

graybg2.png

936 ms

login2.png

login2.png

951 ms

pinterest_icon.png

pinterest_icon.png

978 ms

youtube_icon.png

youtube_icon.png

1001 ms

fb_20.png

fb_20.png

1023 ms

gradient2.png

gradient2.png

1029 ms

widgets.js

widgets.js

225 ms

player-bg.jpg

player-bg.jpg

1028 ms

js

js

223 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

34 ms

fastbutton

fastbutton

100 ms

info.png

info.png

317 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

878 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

1023 ms

dropdwn_arrow.gif

dropdwn_arrow.gif

935 ms

postmessageRelay

postmessageRelay

79 ms

__utm.gif

__utm.gif

37 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

20 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

20 ms

3193398744-postmessagerelay.js

3193398744-postmessagerelay.js

11 ms

rpc:shindig_random.js

rpc:shindig_random.js

35 ms

script_data.js

script_data.js

205 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

in.php

in.php

328 ms

localization.en.1.3632191afe35222a6b78c04d457adc0d_247a7ee5954656184002421d877495fb.js

localization.en.1.3632191afe35222a6b78c04d457adc0d_247a7ee5954656184002421d877495fb.js

51 ms

ping

ping

89 ms

4633-1bh06zu.png

4633-1bh06zu.png

31 ms

SEO Factors

janzz.ch SEO score

0

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 Janzz.ch 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 Janzz.ch 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

janzz.ch

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