Tools & Wizards About Us
zsh.no screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

zsh.no

Oh My Zsh - a delightful & open source framework for Zsh

Page Load Speed

3.6 sec in total

First Response

328 ms

Resources Loaded

1.9 sec

Page Rendered

1.3 sec

zsh.no screenshot

About Website

Click here to check amazing Zsh content for Norway. Otherwise, check out these important facts you probably never knew about zsh.no

Oh My Zsh is a delightful, open source, community-driven framework for managing your Zsh configuration.

Visit zsh.no

Key Findings

We analyzed Zsh.no page load time and found that the first response time was 328 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

zsh.no performance score

0

Network Requests Diagram

zsh.no

328 ms

ohmyz.sh

75 ms

gtm.js

287 ms

style.css

10 ms

fancy.css

72 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Zsh.no, 63% (45 requests) were made to Ohmyz.sh and 17% (12 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (901 ms) relates to the external source Img.shields.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.2 kB (21%)

Content Size

978.7 kB

After Optimization

774.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Zsh.no main page is 978.7 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. 70% of websites need less resources to load. Images take 748.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 63.3 kB

  • Original 74.4 kB
  • After minification 70.3 kB
  • After compression 11.2 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 63.3 kB or 85% of the original size.

Image Optimization

-3%

Potential reduce by 25.6 kB

  • Original 748.2 kB
  • After minification 722.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. Zsh images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 50.3 kB

  • Original 78.4 kB
  • After minification 71.3 kB
  • After compression 28.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 50.3 kB or 64% of the original size.

CSS Optimization

-84%

Potential reduce by 65.0 kB

  • Original 77.7 kB
  • After minification 76.9 kB
  • After compression 12.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. Zsh.no needs all CSS files to be minified and compressed as it can save up to 65.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (21%)

Requests Now

57

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zsh.no

zsh.no

328 ms

ohmyz.sh

ohmyz.sh

75 ms

gtm.js

gtm.js

287 ms

style.css

style.css

10 ms

fancy.css

fancy.css

72 ms

jquery-latest.min.js

jquery-latest.min.js

230 ms

responsiveslides.min.js

responsiveslides.min.js

76 ms

jquery.quovolver.js

jquery.quovolver.js

76 ms

modal.js

modal.js

92 ms

smooth-scroll.min.js

smooth-scroll.min.js

93 ms

script.js

script.js

93 ms

reset.css

reset.css

91 ms

all.js

all.js

481 ms

github-btn.html

github-btn.html

631 ms

github-btn.html

github-btn.html

787 ms

widgets.js

widgets.js

787 ms

buy-button-storefront.min.js

buy-button-storefront.min.js

500 ms

642496866407284746

642496866407284746

901 ms

OMZLogo_BnW.png

OMZLogo_BnW.png

412 ms

nebirhos.jpg

nebirhos.jpg

405 ms

daveverwer.jpg

daveverwer.jpg

411 ms

af-magic.jpg

af-magic.jpg

458 ms

eastwood.jpg

eastwood.jpg

454 ms

kolo.jpg

kolo.jpg

399 ms

mh.jpg

mh.jpg

463 ms

icon-plugins.svg

icon-plugins.svg

459 ms

icon-community.svg

icon-community.svg

457 ms

icon-twitter.svg

icon-twitter.svg

455 ms

logo-git.png

logo-git.png

560 ms

logo-laravel.svg

logo-laravel.svg

558 ms

logo-nodejs.svg

logo-nodejs.svg

557 ms

logo-spotify.png

logo-spotify.png

540 ms

logo-vscode.png

logo-vscode.png

551 ms

logo-postgresql.svg

logo-postgresql.svg

536 ms

logo-ruby.svg

logo-ruby.svg

570 ms

logo-scala.png

logo-scala.png

572 ms

logo-sublime.png

logo-sublime.png

571 ms

logo-python.svg

logo-python.svg

571 ms

logo-rails.svg

logo-rails.svg

595 ms

logo-go.svg

logo-go.svg

692 ms

logo-heroku.svg

logo-heroku.svg

705 ms

logo-terraform.svg

logo-terraform.svg

709 ms

logo-aws.svg

logo-aws.svg

706 ms

logo-kubernetes.png

logo-kubernetes.png

704 ms

logo-docker.png

logo-docker.png

708 ms

logo-react.png

logo-react.png

723 ms

rainbow-robbies.jpg

rainbow-robbies.jpg

793 ms

follow-ohmyzsh.jpg

follow-ohmyzsh.jpg

792 ms

follow-robby.jpg

follow-robby.jpg

791 ms

follow-marc.jpg

follow-marc.jpg

788 ms

logo-discord.svg

logo-discord.svg

788 ms

logo-pa.svg

logo-pa.svg

792 ms

icon-instagram.svg

icon-instagram.svg

803 ms

icon-facebook.svg

icon-facebook.svg

800 ms

all.js

all.js

141 ms

analytics.js

analytics.js

347 ms

iof2xms.js

iof2xms.js

418 ms

ohmyzsh

ohmyzsh

590 ms

collect

collect

36 ms

widget_iframe.7dae38096d06923d683a2a807172322a.html

widget_iframe.7dae38096d06923d683a2a807172322a.html

230 ms

d

d

42 ms

d

d

23 ms

d

d

44 ms

d

d

43 ms

d

d

43 ms

d

d

43 ms

d

d

111 ms

d

d

111 ms

d

d

110 ms

d

d

110 ms

d

d

112 ms

SEO Factors

zsh.no 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 Zsh.no 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 Zsh.no 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

zsh.no

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