Overall Performance Review

Desktop Speed Performance Results
A
B
C
Mobile Speed Performance Results
A
B
C
Domain Rating Results
A
B
C
A
Industry Standard
B
EC Group Performance
C
Growthlabs Clients

SEO Overview Statistics

Total Ranked Keywords
Keywords in #1 Position
Keywords in #2-3 Position
Keywords in #4 - #10 Position
Estimated Traffic Value
$
Highest Search Volume
Top Ranked Keyword
Total Search Volume

Overall Website Statistics

Valid SSL Certificate
Canonicalization Test Passed
WWW Redirect Test Passed
4XX Errors
External Links
Internal Links
Broken Links
Duplicate Titles
Duplicate Descriptions
Duplicate Content Instances
Pages Without Descriptions
Title Too Long
Title Too Short
Redirect Loops
5XX Errors
Broken Resources
SEO-Friendly URL Checks Passed
SEO-Friendly URL Keywords Check
Images With Missing Alt Attributes
Images Missing Image Titles
Website Performance Analysis Report
Overview

The website’s performance scores from PageSpeed Insights indicate significant areas for improvement, particularly in mobile and desktop performance. The Mobile Performance score is 29, while the Desktop Performance score is 40. These low scores suggest that users may experience slow loading times and a less-than-ideal browsing experience.

Performance Scores
  • Mobile Performance: 29
  • Mobile Accessibility: 88
  • Mobile Best Practice: 96
  • Mobile SEO: 92
  • Desktop Performance: 40
  • Desktop Accessibility: 88
  • Desktop Best Practice: 74
  • Desktop SEO: 92
Main Recommendations
1. Minify JavaScript

Minifying JavaScript files can significantly reduce the size of the files and improve loading times. Potential savings of 88 KiB can be achieved. Learn how to minify JavaScript.

2. Serve Static Assets with an Efficient Cache Policy

Implementing a long cache lifetime for static assets can enhance the speed of repeat visits. There are 119 resources identified that can benefit from this practice. Learn more about efficient cache policies.

3. Reduce Unused CSS

By reducing unused CSS rules, the network activity can be decreased, with potential savings of 232 KiB. Learn how to reduce unused CSS.

4. Optimize Images

Properly sizing images and serving them in next-gen formats like WebP can drastically reduce loading times. Potential savings of 891 KiB and 377 KiB can be realized, respectively. Learn how to size images. Learn more about modern image formats.

5. Eliminate Render-Blocking Resources

Identifying and deferring non-critical JavaScript and CSS can reduce the time taken for the first paint of the page, with potential savings of 1,600 ms. Learn how to eliminate render-blocking resources.

6. Defer Offscreen Images

Implement lazy-loading for offscreen images to improve the time to interactive. Potential savings of 1,089 KiB can be achieved. Learn how to defer offscreen images.

7. Reduce JavaScript Execution Time

Reducing the time spent on parsing and executing JavaScript can enhance performance. Consider delivering smaller JS payloads to achieve this. Learn how to reduce JavaScript execution time.

8. Avoid Excessive DOM Size

A large DOM can lead to increased memory usage and longer style calculations. It is recommended to keep the DOM size manageable, currently at 1,020 elements. Learn how to avoid an excessive DOM size.

Conclusion

Improving the website’s performance is crucial for enhancing user experience. By implementing the above recommendations, the website can achieve better loading times and overall performance scores. Prioritizing these changes will lead to a more efficient and user-friendly site.

Get full report

Current Website Issues

Minifying JavaScript files can reduce payload sizes and script parse time. [Learn how to minify JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unminified-javascript/).
A long cache lifetime can speed up repeat visits to your page. [Learn more about efficient cache policies](https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/).
Speed Index shows how quickly the contents of a page are visibly populated. [Learn more about the Speed Index metric](https://developer.chrome.com/docs/lighthouse/performance/speed-index/).
First Contentful Paint marks the time at which the first text or image is painted. [Learn more about the First Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/first-contentful-paint/).
Large network payloads cost users real money and are highly correlated with long load times. [Learn how to reduce payload sizes](https://developer.chrome.com/docs/lighthouse/performance/total-byte-weight/).
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls). [Learn how to improve CLS](https://web.dev/articles/optimize-cls)
Minifying CSS files can reduce network payload sizes. [Learn how to minify CSS](https://developer.chrome.com/docs/lighthouse/performance/unminified-css/).
The maximum potential First Input Delay that your users could experience is the duration of the longest task. [Learn more about the Maximum Potential First Input Delay metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-max-potential-fid/).
Largest Contentful Paint marks the time at which the largest text or image is painted. [Learn more about the Largest Contentful Paint metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)
Time to Interactive is the amount of time it takes for the page to become fully interactive. [Learn more about the Time to Interactive metric](https://developer.chrome.com/docs/lighthouse/performance/interactive/).
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. [Learn how to reduce unused CSS](https://developer.chrome.com/docs/lighthouse/performance/unused-css-rules/).
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. [Learn how to defer third-parties with a facade](https://developer.chrome.com/docs/lighthouse/performance/third-party-facades/).
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. [Learn more about third-party cookies](https://developers.google.com/privacy-sandbox/cookies).
This is the largest contentful element painted within the viewport. [Learn more about the Largest Contentful Paint element](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-largest-contentful-paint/)
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. [Learn more about the Total Blocking Time metric](https://developer.chrome.com/docs/lighthouse/performance/lighthouse-total-blocking-time/).
Serve images that are appropriately-sized to save cellular data and improve load time. [Learn how to size images](https://developer.chrome.com/docs/lighthouse/performance/uses-responsive-images/).
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn how to eliminate render-blocking resources](https://developer.chrome.com/docs/lighthouse/performance/render-blocking-resources/).
Cumulative Layout Shift measures the movement of visible elements within the viewport. [Learn more about the Cumulative Layout Shift metric](https://web.dev/articles/cls).
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn how to defer offscreen images](https://developer.chrome.com/docs/lighthouse/performance/offscreen-images/).
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more about modern image formats](https://developer.chrome.com/docs/lighthouse/performance/uses-webp-images/).
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. [Learn how to use modern JavaScript](https://web.dev/articles/publish-modern-javascript)
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow). [Learn how to avoid an excessive DOM size](https://developer.chrome.com/docs/lighthouse/performance/dom-size/).
Optimized images load faster and consume less cellular data. [Learn how to efficiently encode images](https://developer.chrome.com/docs/lighthouse/performance/uses-optimized-images/).
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to minimize main-thread work](https://developer.chrome.com/docs/lighthouse/performance/mainthread-work-breakdown/)

Techical SEO Report

Technical SEO Report
1. Missing <h1>

Issue: Pages which have a missing <h1>, the content is empty or has a whitespace.

Impact: The <h1> should describe the main title and purpose of the page and are considered to be one of the stronger on-page ranking signals.

Fixes:

  • Ensure important pages have concise, descriptive and unique headings to help users, and enable search engines to score and rank the page for relevant search queries.
2. Page Titles: Same as <h1>

Opportunity: Page titles which match the <h1> on the page exactly.

Impact: This may point to a potential opportunity to target alternative keywords, synonyms, or related key phrases.

Fixes:

  • Consider targeting alternative keywords, synonyms, or related key phrases in page titles.
3. Validation: High Carbon Rating

Opportunity: URLs that have a carbon rating of D, E or F.

Impact: This can contribute to a more sustainable web.

Fixes:

  • Use the digital carbon ratings system from Sustainable Web Design as a benchmark.
4. Hreflang: Not Using Canonical

Issue: URLs not using the canonical URL on the page in its own hreflang annotation.

Impact: Hreflang should only include canonical versions of URLs.

Fixes:

  • Update hreflang annotations to include canonical versions of URLs only.
5. Security: Missing Content-Security-Policy Header

Warning: URLs that are missing the Content-Security-Policy response header.

Impact: This policy can help guard against cross-site scripting (XSS) attacks.

Fixes:

  • Set a strict Content-Security-Policy response header across all pages.
6. Page Titles: Over 561 Pixels

Opportunity: Pages which have page titles over Google’s estimated pixel length limit.

Impact: Important words may be truncated in search results.

Fixes:

  • Write concise page titles to ensure important words are not truncated.
7. Response Codes: External Client Error (4xx)

Warning: External URLs with a client-side error.

Impact: Indicates a problem occurred with the URL request.

Fixes:

  • Update all links on a website to resolve to 200 ‘OK’ URLs.
8. Links: Pages With High External Outlinks

Warning: Pages that have a high number of followed external outlinks.

Impact: External outlinks should be to credible, trusted and relevant websites.

Fixes:

  • Review followed external outlinks to ensure they are useful to your users.
9. Security: Missing X-Frame-Options Header

Warning: URLs missing an X-Frame-Options response header.

Impact: This helps avoid clickjacking attacks.

Fixes:

  • Supply the X-Frame-Options response header with a ‘DENY’ or ‘SAMEORIGIN’ value.
10. Hreflang: Noindex Return Links

Issue: URLs with return links which have a ‘noindex’ meta tag.

Impact: May result in the hreflang relationship being ignored.

Fixes:

  • Update hreflang annotations to include indexable URLs only.
11. Security: Missing X-Content-Type-Options Header

Warning: URLs that are missing the ‘X-Content-Type-Options’ response header.

Impact: This can be exploited by attackers.

Fixes:

  • Supply the X-Content-Type-Options response header set to ‘nosniff’.
12. Canonicals: Missing

Warning: Pages that have no canonical URL present.

Impact: Can lead to ranking unpredictability.

Fixes:

  • Specify a canonical URL for every page.
13. URL: Over 115 Characters

Opportunity: URLs that are more than the configured length.

Impact: Users prefer shorter, concise URL strings.

Fixes:

  • Use logical and concise URLs where possible.
14. Page Titles: Below 30 Characters

Opportunity: Pages which have page titles under the configured limit.

Impact: Indicates there might be room to target additional keywords.

Fixes:

  • Consider updating the page title to include additional target keywords.
15. Response Codes: Internal Redirection (3xx)

Warning: Internal URLs which redirect to another URL.

Impact: This reduces efficiency for search engines.

Fixes:

  • Avoid linking to URLs that redirect.
16. Images: Missing Alt Text

Issue: Images that have an alt attribute, but are missing alt text.

Impact: Helps the blind and visually impaired, and search engines understand images.

Fixes:

  • Include descriptive alt text for images.
17. Security: Missing HSTS Header

Warning: URLs that are missing the HSTS response header.

Impact: Instructs browsers to only access using HTTPS.

Fixes:

  • Use the HSTS header across all pages.
18. Links: Internal Outlinks With No Anchor Text

Opportunity: Pages that have internal links without anchor text.

Impact: Provides context about the content of the target page.

Fixes:

  • Include useful and descriptive anchor text for internal outlinks.
Get full report

Tech Stack Report

Website Structure and Technology Stack Assessment

The website utilizes a variety of technologies and plugins that contribute to its functionality and performance. However, the PageSpeed Insights scores indicate that there are significant areas for improvement, particularly in mobile and desktop performance.

Performance Overview
  • Mobile Performance: 29
  • Mobile Accessibility: 88
  • Mobile Best Practice: 96
  • Mobile SEO: 92
  • Desktop Performance: 40
  • Desktop Accessibility: 88
  • Desktop Best Practice: 74
  • Desktop SEO: 92
Technology Stack

The website employs a range of tools and plugins, including:

  • CRM and Marketing Automation: “HubSpot”
  • Analytics: “Google Analytics”, “Google Analytics 4”, “Microsoft Clarity”
  • SEO: “RankMath”
  • WordPress Plugins: “Contact Form 7”, “Elementor”, “Slider Revolution”, “Wordfence”, “LiteSpeed Cache”
  • Content Delivery Network: “CloudFront”, “Cloudflare”
  • JavaScript Libraries: “jQuery”, “GSAP”
Recommendations for Improvement
1. Optimize Performance

Given the low performance scores, it is essential to optimize the website for better loading times.

  • Minimize the use of heavy plugins such as “Slider Revolution” and “Elementor” if they are not critical to the site’s functionality.
  • Consider using a more efficient caching solution, ensuring that only one caching plugin is active to avoid conflicts.
2. Review and Update Plugins

Some plugins may be outdated or bloated, affecting performance.

  • Evaluate the necessity of plugins like “Stream” and “Redirection for Contact Form 7”, which may add unnecessary overhead.
  • Ensure all plugins are updated to their latest versions to benefit from performance improvements and security patches.
3. Improve Mobile Performance

With a mobile performance score of 29, focusing on mobile optimization is crucial.

  • Implement responsive design principles to enhance mobile user experience.
  • Reduce image sizes and utilize modern formats such as “WebP”.
4. Enhance Accessibility

While accessibility scores are decent, there is always room for improvement.

  • Conduct a thorough accessibility audit to identify areas for improvement, such as color contrast and keyboard navigation.
  • Ensure all images have appropriate “alt” tags for better screen reader compatibility.
5. SEO Best Practices

Although SEO scores are satisfactory, optimizing further can drive more organic traffic.

  • Regularly update content to keep it fresh and relevant.
  • Utilize structured data to enhance search visibility.
Get full report

SEO Report

SEO Analysis Report
Overview

This report analyzes the SEO strengths and weaknesses of the website based on Ahrefs data and PageSpeed Insights scores. The scores indicate areas of performance, accessibility, best practices, and SEO effectiveness on both mobile and desktop platforms.

Current Rankings

The current rankings of the website are influenced by various factors including keyword usage, backlinks, and site performance. The following sections will delve into specific strengths and weaknesses.

Keywords

Keyword analysis is crucial for understanding the visibility of the website in search engine results. A thorough examination of the top-ranking keywords can reveal opportunities for optimization and content development.

Strengths
Mobile Accessibility

With a score of 88, the website demonstrates strong mobile accessibility. This indicates that users on mobile devices can navigate the site effectively, which is essential for user experience and retention.

Mobile Best Practices

The website scored 96 in mobile best practices, showcasing adherence to recommended guidelines. This can positively impact user experience and potentially improve rankings in mobile search results.

SEO Scores

The mobile SEO score of 92 suggests that the website is well-optimized for search engines on mobile devices. Similarly, the desktop SEO score of 92 indicates a consistent approach to SEO across platforms.

Weaknesses
Mobile Performance

Despite strong accessibility and best practices, the mobile performance score is only 29. This low score indicates potential issues with loading times and responsiveness, which can lead to higher bounce rates and lower user satisfaction.

Desktop Performance

The desktop performance score of 40 also reflects significant room for improvement. A slower desktop experience can deter users and negatively affect search engine rankings.

Desktop Best Practices

A score of 74 in desktop best practices suggests that while the site follows many recommended guidelines, there are still areas that need attention to enhance overall site performance and user experience.

SEO Strategies
Recommendations

To capitalize on the strengths and address the weaknesses identified, the following strategies are recommended:

  • Optimize images and resources to improve mobile and desktop performance scores.
  • Conduct a thorough audit of the website’s loading times and implement caching strategies.
  • Enhance keyword targeting and content strategy to improve visibility in search engine results.
  • Regularly monitor performance metrics to ensure ongoing compliance with best practices.
Conclusion

Overall, while the website has strong SEO scores in accessibility and best practices, significant improvements are needed in performance metrics on both mobile and desktop platforms. Addressing these weaknesses will enhance user experience and potentially improve search engine rankings.

Get full report

Want to know what your competitors are doing?

How do you compare to your competitors?
Get detailed market knowledge with a Competitor Insight review. See where you stand and the opportunities where you can out-perform. Identify the strengths and weaknesses of your competitor websites and take away a plan for gaining valuable search traffic.

We can only provide a limited number of Competitor Insight reviews so click below to request access to this invaluable analysis.

A Growthlabs Competitor Insight review includes:
Detailed analysis of your top 5 competitors
Review discussion with member of the Growthlabs team
Recommendations and an action plan
Only 20 Deep Dive reviews available.
Request Competitor Insight
How do you compare to competitors?
Get Competitor Insight
Curious how you stack up against your competitors?
Get a Competitor Insight review from Growthlabs to see where you stand, uncover key opportunities, and walk away with a clear plan to gain valuable search traffic. Limited to just 20 reviews—complete the form below to request yours.