photo description
Tutorial - Optimize PageSpped

SEO Marketing

Optimize PageSpeed


After diagnosing any Performance issues with PageSpeed Insights, you will be informed of solutions or Opportunities to correct with Estimated Savings of load time.

Learn more about PageSpeed Insights ›
PageSpeed Scoring for your visitors

Interpreting the Scoring for Websites

33 Performance
53 Accessibility
61 Best Practices
98 SEO
Performance
Accessibility
Best Practices
SEO
Quality Score:
90 - 100
50 - 89
0 - 49
*Source: PageSpeed Insights

*Example of Google PageSpeed Insights scoring.

SEO Score:
When attempting to optimize, an SEO score of 90 or higher is simple to achieve because this metric only measures basic on-page SEO factors (i.e. Title tag, Meta tags, ALT tags, etc).

Performance Score:
A high Performance score could be more difficult to achieve because it requires the webpage, files, and media to load efficiently.

If your website does not load efficiently, it can negatively affect the bounce rate, which in turn will decrease SEO. Thus, it is important to consider your website platform. A light-weight html website is ideal for Page Speed.

However, for convenience and cost-effectiveness, most website owners opt for a Content Management System (CMS), such as WordPress, Drupal, etc.
This can be problematic for Page Speed, because CMS platforms typically use excessive overhead and unused code.
If you still prefer to use a CMS system, you should try out different templates to see which one(s) score well on Google PageSpeed Insights.
Troubleshooting

A Comprehensive List of SEO & PageSpeed Issues

Performance:
  • Reduce unused JavaScript
  • Preload Largest Contentful Paint image
  • Properly size images
  • Defer offscreen images
  • Serve images in next-gen formats
  • Enable text compression
  • Eliminate render-blocking resources
  • Reduce initial server response time
  • Efficiently encode images
  • Avoid serving legacy JavaScript to modern browsers
  • Minify JavaScript
  • Reduce unused CSS
  • Remove duplicate modules in JavaScript bundles
  • Minimize main-thread work
  • Ensure text remains visible during webfont load
  • Reduce the impact of third-party code
  • Largest Contentful Paint image was lazily loaded
  • Does not use passive listeners to improve scrolling performance
  • Image elements do not have explicit width and height
  • Minimize main-thread work
  • Reduce JavaScript execution time
  • Serve static assets with an efficient cache policy
  • Avoid chaining critical requests
  • Largest Contentful Paint element
  • Avoid large layout shifts
  • Avoid long main-thread tasks
  • Avoid an excessive DOM size
  • Avoid enormous network payloads
  • User Timing marks and measures
  • Avoid non-composited animations
  • Avoid document.write()


Accessibilty:
  • Buttons do not have an accessible name
  • Image elements do not have [alt] attributes
  • Image elements have [alt] attributes that are redundant text.
  • Form elements do not have associated labels
  • Links do not have a discernible name
  • Links rely on color to be distinguishable.
  • Values assigned to role="" are not valid ARIA roles.
  • Background and foreground colors do not have a sufficient contrast ratio.
  • Heading elements are not in a sequentially-descending order
  • [user-scalable="no"] is used in the element or the [maximum-scale] attribute is less than 5.
  • Select elements do not have associated label elements.
  • < frame > or < iframe > elements do not have a title
  • Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
  • [aria-*] attributes do not have valid values
  • [aria-*] attributes do not match their roles
  • [aria-*] attributes are not valid or misspelled
  • [aria-hidden="true"] elements contain focusable descendents
  • ARIA IDs are not unique
  • Elements with role="dialog" or role="alertdialog" do not have accessible names.
  • Values assigned to role="" are not valid ARIA roles.
  • [id] attributes on active, focusable elements are not unique
  • List items (< li>) are not contained within < ul>, < ol> or < menu> parent elements.
  • Some elements have a [tabindex] value greater than 0
  • Elements with visible text labels do not have matching accessible names.
  • < object> elements do not have alternate text
  • Lists do not contain only < li> elements and script supporting elements (< script> and < template>).
  • < video> elements contain a < track> element with [kind="captions"]


Best Practices:
  • Browser errors were logged to the console
  • Issues were logged in the Issues panel in Chrome Devtools
  • Missing source maps for large first-party JavaScript
  • Displays images with incorrect aspect ratio
  • Ensure CSP is effective against XSS attacks
  • Uses deprecated APIs
  • Registers an unload listener
  • Serves images with low resolution
  • Requests the geolocation permission on page load
  • Page lacks the HTML doctype, thus triggering quirks-modeDocument must contain a doctype


SEO:
  • robots.txt is not valid
  • Image elements do not have [alt] attributes
  • Links are not crawlable
  • Tap targets are not sized appropriately
  • Links do not have descriptive text
  • Document uses plugins
  • Document does not have a meta description
  • Document doesn't have a valid hreflang
  • Document does not have a valid rel=canonical
  • Page has unsuccessful HTTP status code
  • Document doesn't use legible font sizes
  • Structured data is not valid
  • Document doesn't have a < title> element
  • Does not have a < meta name="viewport"> tag with width or initial-scale
  • Document doesn't use legible font sizes
  • Page has an unsuccessful HTTP status code
  • Page is blocked from indexing


Learn more at https://developers.google.com/speed
Common CMSs

Content Management Systems (CMS): The DYI, Modular Approach



Ranking - PageSpeed Performance for Common CMSs:
  • WordPress
  • Weebly
  • Typo3
  • Bigcommerce
  • Wix
  • Zoho
  • Squarespace
  • Stripe
  • Force (Salesforce Platform)
  • Zendesk
  • WooCommerce
  • Joomla
  • Shopify
  • Magento / Adobe Commerce
  • Drupal
  • Godaddy

CMS Advantages:
  • Free typically
  • User friendly
  • Easy Content Management
  • DIY
  • Fast Launch
  • Modular
  • Community-Driven Forums for Troubleshooting
  • Flexible for adding features
  • Wide range of Templates and Options
  • Quick Template Changes

CMS Disadvantages:
  • Excessive Overhead and Unused Code
  • Potentially Slow PageSpeed
  • Limited Customization
  • Limited Layout Options
  • Recurring Security Update Requirements
  • High Visibility for Hackers
  • High Risk of Security Issues, including private data theft, injection and penetration
  • High Risk of Spam
  • Deprecation Issues
  • Possible Incompatibility Issues with Plug-Ins or Add-Ons



Next Step: Learn how to Research Keywords ›