Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

resolves #6 - minor grammer/spelling fix #17

Merged
merged 1 commit into from
Oct 6, 2019
Merged

resolves #6 - minor grammer/spelling fix #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 17 additions & 17 deletions docs/standards_performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,27 +1,27 @@
# Quaco performance standards

Quaco encourages people to develop a fast loading theme. Partly because [#3 in the top 3 SEO factors](https://www.searchenginejournal.com/top-3-google-factors/308147/#close) is performance. Quaco has build-in tools that do about 70% of the work, the other 30% must be achieved by the programmer but don't worry, we got your back.
Quaco encourages people to develop a fast loading theme. Partly because [#3 in the top 3 SEO factors](https://www.searchenginejournal.com/top-3-google-factors/308147/#close) is performance. Quaco has build-in tools that do about 70% of the work, the other 30% must be achieved by the programmer but don't worry, we got your back.

Besides performance optimization the most important thing in SEO is content, if you are interested, go ahead and read about [Quaco SEO standards](asdasd).
Besides performance optimization the most important thing in SEO is content, if you are interested, go ahead and read about [Quaco SEO standards](https://github.com/beumerr/quaco/blob/master/docs/standards_seo.md).

**If there is an item on this list that shouldn't be there then don't hesitate** [join us on Discord](https://discord.gg/dxVNGtJ) **and start a fight.**

| #Nr | Allergic to | Reaction| Why |
|--|--|--|--|
| **#1** | No Gzipping | :skull: | Gzipping compresses files sizes even further than minifying them. They can reduce loading times up to 75%. |
| **#2** | Uncompressed images | :skull: | Images are loading time killer #1. An uncompressed image of 2.5mb weighs as much as 86 HTML pages weighing 29kb each. Compressing an image without noticeable loss of quality can, in some cases, reduce the size up to 1 / 100th of its original format. An image of 150x150 should not weigh more than 10kb. |
| **#3** | HTTP | :skull: | Domains without HTTP'S' <- are not save and therefor Google doesn't like them that much
| **#4** | Single page sites | :skull: | Although single page sites are very popular here are [5 reasons why they are bad for SEO](https://seo-hacker.com/single-page-websites-bad-seo/) |
| **#5** | Large ammount of request | :skull: | The more request, the longer the que, the more loading. The type of request doesn't matter (img, xhr, ws, css, doc, etc.). Any resource should be combined as much as possible.|
| **#6** | Ajax without history | :skull: | If navigating happens based on XML requests (AJAX) make sure to use history and load content according to slugs, GET request should also be cacheable |
| **#7** | jQuery | :skull: | Every browser support vanilla JS so please stop adding jQuery to improve productivity instead of quality.|
| **#8** | No .min files | :skull: | Minifying your files (also dynamic page with sitemap pre-cashing to static html files) can reduce loading times up to 70% |
| **#9** | JS in `<head>` | :skull: | JS in your head delays primary content from being loaded. If your site uses JS to compile then it could be possible that you are dealing with a mature design fault. |
| **#10** |More than 1 CSS file| :broken_heart: | I know.. A big CSS file is messy but the amount of request ways more than your organized file structure. *(The best way is to compile CSS based on device/viewport... feature request? :D)*|
| **#11** |More than 2 JS files| :broken_heart: | For 1 page there shouldn't be more then 2 JS files. One for your overall 'scripts', the other 'page' related |
| **#12** | No browser cache | :broken_heart: | Just like Gzip, cache has to do everything with loading times. If an HTTP request is still fresh local storage will be consulted instead of re downloading. |
| **#13** | Inline JS/CSS | :broken_heart: | Some people might argue inline CSS because it can increase render times if you only use CSS that before the folt |
| **#1** | No Gzipping | :skull: | Gzipping compresses file size even further than minifying them. They can reduce loading times up to 75%. |
| **#2** | Uncompressed images | :skull: | Images are the #1 loading time killers. An uncompressed image of 2.5mb weighs as much as 86 HTML pages weighing 29kb each. Compressing an image without noticeable loss of quality can, in some cases, reduce the size up to 1 / 100th of its original format. An image of 150x150 should not weigh more than 10kb. |
| **#3** | HTTP | :skull: | Domains without HTTP'S' <- are not safe and therefore Google doesn't like them that much. |
| **#4** | Single page sites | :skull: | Although single page sites are very popular here are [5 reasons why they are bad for SEO](https://seo-hacker.com/single-page-websites-bad-seo/). |
| **#5** | Large number of requests | :skull: | The more requests, the longer the queue and loading time. The type of request doesn't matter (img, xhr, ws, css, doc, etc.). Any resource should be combined as much as possible. |
| **#6** | Ajax without history | :skull: | If navigating happens based on XML requests (AJAX) make sure to use history and load content according to slugs, GET request should also be cacheable. |
| **#7** | jQuery | :skull: | Every browser supports vanilla JS so please stop adding jQuery to improve productivity instead of quality. |
| **#8** | No .min files | :skull: | Minifying your files (including dynamic pages with sitemap pre-cashing to static html files) can reduce loading times up to 70%. |
| **#9** | JS in `<head>` | :skull: | JS in your `<head>` delays primary content from being loaded. If your site uses JS to compile then it could be possible that you are dealing with a mature design fault. |
| **#10** |More than 1 CSS file| :broken_heart: | I know.. A big CSS file is messy but the number of requests weighs more than your organized file structure. *(The best way is to compile CSS based on device/viewport... feature request? :D)* |
| **#11** |More than 2 JS files| :broken_heart: | For 1 page there shouldn't be more then 2 JS files. One for your overall 'scripts', the other 'page' related. |
| **#12** | No browser cache | :broken_heart: | Just like Gzip, cache has to do everything with loading time. If an HTTP request is still fresh, local storage will be consulted instead of re-downloading. |
| **#13** | Inline JS/CSS | :broken_heart: | Some people might argue inline CSS because it can increase render times if you only use CSS that is before the folt. |
| **#14** | Expire header | :lemon: or :skull: | Expires headers tell the browser whether a resource on a website needs to be requested from the server or fetched from local storage. If dynamic content has a long expire date, fresh content will not be visible. |
| **#15** | CDN | :lemon: | When using a content delivery network, visitors worldwide will be connected to the nearest proxy server reducing loading items |
| **#15** | CDN | :lemon: | When using a content delivery network, visitors worldwide will be connected to the nearest proxy server reducing loading items. |

*There are many more optimization with lower priority that we didn't put in this list, feel like its missing important aspects? Get in contact.*
*There are many more optimizations with lower priority that we didn't put in this list, feel like its missing important aspects? Get in contact.*