(#11) page speed test:

  1. targets are < 2 seconds for an initial view, < 1 second for a cached view
  2. your home page: 6.6 seconds initial, 2.7 seconds cached
  3. PageSpeed insights is giving the page a score of 43 for mobile, and 79 for desktop (that's pretty good, but we'd like to see it over 60 if possible)
    1. the most common reason for low PageSpeed Insights mobile scores is too many http requests
    2. it seems that they're simulating a cell connection type that would only permit a single connection (versus 6 parallel connections like a desktop browser would use)
  4. recommendations:
    1. remove unused rules from your stylesheets – potential here to save 1.65 seconds
    2. resize your images to the sizes they're actually used at, rather than making the browser download a much larger image and then resize it:
      1. https://www.countrysideday.org/wp-content/themes/twentynineteen/img/img4.jpg is resized in HTML or CSS from 888x827 to 375x349. Serving a scaled image could save 70.0KiB (82% reduction).
      2. https://www.countrysideday.org/wp-content/themes/twentynineteen/img/img3.jpg is resized in HTML or CSS from 815x828 to 375x381. Serving a scaled image could save 65.2KiB (78% reduction).
      3. https://www.countrysideday.org/wp-content/themes/twentynineteen/img/img5.jpg is resized in HTML or CSS from 871x705 to 375x304. Serving a scaled image could save 59.8KiB (81% reduction).
    3. leverage browser caching by specifying expiry dates in your HTTP headers for your PNG, JPG, and ICO files
    4. don't embed an MP4 video – use Wistia instead
    5. defer parsing of Javascript, especially the opmnstr.com api.min.js
    6. combine all of your JS files into a single file, and save 15 http requests
    7. combine all of your CSS files into a single file, and save 10 http requests

      VVT comment for 11: priority  - HIGH, but we recommend converting JPG and PNG to WebP (covered in the previous item) and adding a caching plugin for WordPress (3 hours)

(#28) Google Search Console:

  1. XML sitemaps and indexation:
    1. you've got 2 XML sitemaps submitted in Search Console – this one doesn't exist, so delete it:
      1. https://www.countrysideday.org/sitemap/sitemap.xml
    2. 289 URLs submitted in the other sitemap
  • need to change http to https for all URLs in your XML sitemap
  1. 101 indexed from the sitemap; another 270 were not in the XML sitemap, but were discovered and indexed
    1. 29 are author or category archive pages, which should be noindexed
    2. 9 are faqs or tag archives pages, which should be noindexed
    3. 24 are PDFs which don't seem to have links to them any more
    4. a handful of them 404 now, and will disappear on their own, including a bunch of landing pages like this
    5. a bunch of them are numbered blog archives pages, which should be noindexed
    6. 13 of them are WP plugins URLs which no longer exist (they'll go away on their own too)
  2. my crawler only found 159 indexable URLs
  3. 148 seen as duplicates – because they're http, not https
  4. 24 are crawled, but not indexed
    1. these are tag and category archives pages – which should be noindexed, and NOT in your XML sitemaps
    2. also there are FAQ fragment pages – these also should be noindexed, and NOT in your XML sitemaps
  5. 16 are discovered but not indexed – these may end up getting indexed once Googlebot actually crawls them
    VVT comment for 28a: priority - MEDIUM we will need to work with the XML (5 hours)