Site icon EZ Indie Publishing ~ Elisabeth Zguta Indie Author ~

Optimizing Your Sites-To Be Seen

jeune-femme-et-ordinateur-portable
Photo by axelle b. Check her work at Public Domain Pictures

Marketing, there’s talk going on but lately, it sounds repetitive. We’ve all been blasted with the obvious: Write a good book, use meta tags wisely, create a platform, utilize social media in a non-spammy way and connect with network movers. We’ve also heard that Google made changes to their algorithm again!

So what’s a writer to do but try to be creative, write original content, and be helpful. It’s rather vague and in my opinion and it’s subjective, but they rule (Google and Amazon browsers). So we go along for the ride, we use the tags #IndieBooksBeSeen #IndieAuthors and the like (at least I hope you do). BUT there’s more you can do . . .

There are steps we can take to keep our content in good performance mode and readily available for the search engines to read our stuff.

Start with a check-up.

SEO – search engine optimization is alive, it grows, it changes, it drives our content. So if you want your stuff to be read, use any tools you can to get your sites tuned up.

For your website checkup use the Google PageSpeed Insights:

https://developers.google.com/speed/pagespeed/

Here are some good pointers which I intend to implement on my sites:

I hope this information helps you strengthen your sites. When an Indie Author’s work is seen we all win.

Keep reading – Keep writing!

One Last TIP: One of the most common problems with websites is slow response time and reducing the cache.

Check out this help below from Ilya Grigorik, a Developer Advocate and Web Perf Guru

Caching checklist

There is no one best cache policy. Depending on your traffic patterns, type of data served, and application-specific requirements for data freshness, you will have to define and configure the appropriate per-resource settings, as well as the overall “caching hierarchy”.

Some tips and techniques to keep in mind as you work on caching strategy:

  1. Use consistent URLs: if you serve the same content on different URLs, then that content will be fetched and stored multiple times. Tip: note that URLs are case sensitive!
  2. Ensure the server provides a validation token (ETag): validation tokens eliminate the need to transfer the same bytes when a resource has not changed on the server.
  3. Identify which resources can be cached by intermediaries: those with responses that are identical for all users are great candidates to be cached by a CDN and other intermediaries.
  4. Determine the optimal cache lifetime for each resource: different resources may have different freshness requirements. Audit and determine the appropriate max-age for each one.
  5. Determine the best cache hierarchy for your site: the combination of resource URLs with content fingerprints and short or no-cache lifetimes for HTML documents allows you to control how quickly updates are picked up by the client.
  6. Minimize churn: some resources are updated more frequently than others. If there is a particular part of resource (e.g. JavaScript function, or set of CSS styles) that are often updated, consider delivering that code as a separate file. Doing so allows the remainder of the content (e.g. library code that does not change very often), to be fetched from cache and minimizes the amount of downloaded content whenever an update is fetched.
Authors

Ilya is a Developer Advocate and Web Perf Guru

Exit mobile version