Website Performance Overview

A fast, healthy website is important for providing a good experience to visitors, maintaining search visibility, and avoiding performance-related issues.

Siteligent provides performance diagnostics that help you monitor your website's speed, identify potential bottlenecks, and track important performance metrics over time. Performance data is powered by integration with Google PageSpeed Insights.

Siteligent reports several metrics that help you understand how your website is performing.

The Performance Score is a score from 0 to 100 based on Google Lighthouse's assessment of your site's performance.

It takes factors such as loading speed and resource size into account.

The SEO Score evaluates aspects of your website that affect how easily search engines can discover and index your pages.

Time to First Byte (TTFB) measures how quickly your server starts responding to a request.

Siteligent measures this by sending a direct HTTP HEAD request to your site's homepage. A high TTFB can indicate that the server is taking too long to begin responding, which may require further investigation.

Load Time represents the overall time required for your website to load and become fully interactive.

This gives you a broader view of the visitor's loading experience rather than looking only at the initial server response.

Siteligent also reports on Core Web Vitals, which focus on how users actually experience a page.

LCP measures how quickly the main content of a page becomes visible. A slow LCP can make a page feel slow even when other parts of the page have already started loading.

FID / INP measures how responsive the page is when visitors interact with it.

These metrics help identify situations where a page appears to have loaded but doesn't respond quickly to clicks, taps, or other interactions.

CLS measures visual stability. It helps identify unexpected movement of page elements while the page is loading, such as text or buttons suddenly shifting position after another element loads.

Siteligent can run performance scans automatically so you don't have to manually test every site.

The automated scheduler queries Google PageSpeed Insights every two days at 2:00 AM UTC for connected sites. The results are stored so you can track performance over time through the historical charts.

This is useful for identifying gradual performance changes that may otherwise go unnoticed.

You can also run a performance scan whenever you want.

Manual tests run for both:

The two tests can be triggered in parallel.

Manual scans bypass the cached results and query Google PageSpeed Insights directly. This makes them particularly useful immediately after making a performance-related change, for example, after optimizing images, changing a caching configuration, or modifying your site's front-end code.

AI Performance Analysis helps you understand what is slowing down your website and gives you specific recommendations for improving its performance.

Instead of only showing a performance score, Zyra AI analyzes the performance data and identifies individual improvements that could help increase your speed score.

View Performance Recommendations

When Zyra AI analyzes your site, it can show:

For example, Zyra AI may identify unused CSS as an opportunity and explain that removing it could reduce the amount of CSS loaded by the browser. It can then suggest an action such as enabling Remove Unused CSS in a compatible optimization plugin.

It can also identify unused JavaScript and recommend reducing scripts that aren't needed on specific pages.

Estimated Performance Improvements

Zyra AI groups its recommendations and estimates the potential impact of each improvement.

For example, the analysis may show:

These estimates are intended to help you prioritize the changes that are likely to have the greatest impact rather than making performance changes without knowing where to start.

Follow the Recommended Fix

Each recommendation can include a suggested action that points you toward a practical way to address the issue.

For example:

Another recommendation might be:

This makes the analysis more actionable: you can see what the problem is, why it matters, the potential impact, and what to do next.

Prioritize High-Impact Improvements

You don't necessarily need to implement every recommendation at once. Start with the recommendations showing the largest potential performance improvement, then run another performance analysis after making the changes.

This gives you a practical way to work through performance optimization step by step and measure whether the changes actually improved your site's results.

Performance scores are most useful when you look at them over time rather than focusing on a single test result.

For example, if a site's performance score drops after a plugin update, a new theme change, or a significant content change, you can use the other diagnostic tools in Siteligent to investigate what changed.

Performance monitoring can therefore be used as an early warning system: track the metrics, identify changes, and investigate significant regressions before they become a larger problem for visitors.