1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
|
---
title: "Page Quality"
date: 2022-03-21
tags: ["server"]
---
After you\'ve deployed your website, you may want to consider improving
its performance, accessibility, and search-engine optimization (SEO).
Doing so can help make your website more user-friendly and increase its
page rank in search results. Luckily, Google provides a [measurement
tool](https://web.dev/measure) to help you improve these aspects. Start by
entering your website\'s URL and click the _Run Audit_ button (it will
take 5-10 seconds to generate the report).
Once the report has finished, you\'ll be greeted by a score for four
different categories: _Performance_, _Accessibility_, _Best Practices_,
and _SEO_. A lot of the tests listed are self-explanatory, and Google
provides you with articles to help you pass them. Below are some easy
ways to improve your scores, some specific to the nginx configuration
used in the [sich website tutorial.](/basic/nginx)
## Performance
### Serving static assets with an efficient cache policy
Serving your files with an efficient cache policy will allow the user\'s
browser to cache files such as pictures and CSS so that the browser doesn\'t
need to fetch these files each time the page is visited.
It\'s very easy to set this up in nginx. Just paste the following within the
server block of your website\'s configuration file:
```nginx
# Media: images, icons, video, audio, HTC
location ~* \.(?:jpg|jpeg|gif|png|ico|svg|webp)$ {
expires 1M;
access_log off;
# max-age must be in seconds
add_header Cache-Control "max-age=2629746, public";
}
# CSS and Javascript
location ~* \.(?:css|js)$ {
expires 1y;
access_log off;
add_header Cache-Control "max-age=31556952, public";
}
```
You can add more types of file extensions (mp3, mp4, ogg) as you see
fit.
If you\'re changing your CSS files a lot, caching could keep repeat
users from getting the most up-to-date stylesheet. To combat this, you
can version your stylesheets like so:
```html
<link rel="stylesheet" type="text/css" href="style.css?v=1.0.0" />
```
Just increase the version number whenever you update your stylesheet,
and the browser will re-update its cache.
### Enable text compression
Another easy addition to your websites configuration file. Enabling text
compression is easy and will save bandwidth for users. Simply paste the
following within the server block of your website\'s configuration file:
```nginx
gzip on;
gzip_min_length 1100;
gzip_buffers 4 32k;
gzip_types text/plain application/x-javascript text/xml text/css;
gzip_vary on;
```
After reloading nginx, you can test if compression is working by opening
your browsers developer tools and going to the network tab. Refresh your
website with the network tab, click on the item with your URL and look
at the response headers. You should see `Content-Encoding: gzip` as one
of the headers displayed.
### Properly sizing images
If you\'ve put images on your webpage, you\'ve most definitely gotten
this warning. To pass this audit, you\'ll need to scale your images down
using a tool like gimp or imagemagick to a size appropriate for your
website. It doesn\'t make much sense to serve a high-res image for
images that are rendered much smaller on a webpage.
Once you\'ve scaled your image down, you can use a tool like `cwebp` to
convert your images into the .webp format, a format specifically created
for serving bandwidth concious images.
First, you\'ll have to install the webp package:
```sh
apt install webp
```
Now you can easily convert your images to webp (keep in mind that it\'s
much more effective to first size your images appropriately before
this). Using the below command, you can specify the quality of the photo
with the `q` option. I typically shoot for a quality in the range of
60-80, depending on the image and how large it will be displayed on the
webpage.
```sh
cwebp -q 80 your-photo.png -o your-photo.webp
```
You can now check the difference in size of the images using `ls`.
```sh
ls -lh your-photo*
```
After utilizing webp images, the audit typically goes away, but if you
didn\'t scale your image properly before hand, it may still linger.
## Accessibility
### Image elements do not have \[alt\] attributes
It may seem silly to add `alt` attributes to images, but it helps screen
readers convey images to users and can help page rank as a result. The
`alt` attribute should simply describe the image being displayed.
```html
<img src="img/cabin.webp" alt="A cabin nestled between pine trees" />
```
## SEO
### Document does not have a meta description
Adding meta descriptions to your webpage allow for web-crawlers and bots
to easily determine what content your website contains. Just like on
other online platforms, you can give your webpage a long list of
keywords to help increase the chance someone stumbles upon your site
from a search engine. You don\'t need to add all of the below meta tags
to pass the audit, only add what\'s necessary.
```html
<!--- Instructions for web scrapers --->
<meta name="robots" content="index, follow" />
<meta name="description" content="your website description" />
<meta name="keywords" content="your, keywords, here" />
<meta name="author" content="your name" />
<!--- Facebook specific standard, but many websites use this so it has become almost standard to include --->
<meta property="og:site_name" content="Site Name" />
<meta name="twitter:domain" property="twitter:domain" content="example.org" />
<meta name="og:title" property="og:title" content="Site Name" />
<meta property="og:description" content="your website description" />
<meta
name="twitter:description"
property="twitter:description"
content="your website description"
/>
<meta
name="og:image"
content="https://link-to-an-image-that-represents-your-site"
/>
<!--- below is for twitter sharing previews
you can test this at cards-dev.twitter.com --->
<meta
property="twitter:card"
content="https://link-to-an-image-that-represents-your-site"
/>
<meta
name="twitter:image:src"
property="twitter:image:src"
content="https://link-to-an-image-that-represents-your-site"
/>
<meta
name="twitter:image"
property="twitter:image"
content="https://link-to-an-image-that-represents-your-site"
/>
<meta
name="og:image:alt"
property="og:image:alt"
content="alt text for your image"
/>
<meta property="og:url" content="example.org" />
<meta property="og:type" content="website" />
<!--- If you have accounts on twitter or facebook that are relevant to your site --->
<meta property="fb:admins" content="facebook group" />
<meta
name="twitter:site"
property="twitter:site"
content="@yourTwitterHandle"
/>
<meta
name="twitter:creator"
property="twitter:creator"
content="@yourTwitterHandle"
/>
```
---
_Written by [Jacob.](https://mccor.xyz) Donate Monero
[here.](https://mccor.xyz)_
|
