Everything about SitePulse, explained.

A free check gives you the summary: the scores that could be measured, the letter built from them, and a short look at what was found. The long explanations, the full recommendation list and the PDF stay with the paid report. The free page is deliberately shorter, so the paid report is the one you keep and share.

Missing measurements are marked as unavailable. They are not turned into a zero and they are not counted as a failure. If speed could not be measured, the rest of the check still finishes.

No. Paste the public address and start. If you leave off https://, SitePulse adds it. The check reads the public page, the server response, the certificate and the technical signals a visitor can already see. You do not give SitePulse a password, an admin login or FTP access for this.

The WordPress plugin is optional. It is for people who want the report inside WordPress, a schedule, and, with Pro, buttons that change the site. The analysis of a public address does not need it.

One run looks at the public homepage from outside. Speed is measured for a phone and for a desktop, together, with a deadline so a slow lab does not freeze the whole report. The performance score prefers the phone result. Structure, security headers, the certificate, the visible files and the images are read from the same visit.

You then get a letter, category scores, a filmstrip and screenshots when the lab returned them, a list of problems, a table of images, and advice written in the language of the page you started from. The advice explains the finding and gives numbered steps. It does not promise that a score will jump by a certain number.

Each category is its own score. The letter is the average of performance and structure, not a vague overall mark. A missing category is left out and the report says the result is partial. A zero only appears when a check really returned zero.

Open the tabs on the report for speed, files, problems and advice. Each metric can show a short explanation of what the number means. Use the problems and the advice to decide what to do first. The letter alone is not the whole report.

The report names the city and country of the server that actually ran the measurement, plus the Chrome and Lighthouse versions used for that run. That location is the real exit of the measurement server. It is looked up and remembered for a week, then checked again. It is not a label we invented, and it is not described as Google.

A screenshot appears in the progress window only after it has really been captured. Until then the frame stays empty. The filmstrip, when the lab returned one, shows the page as it painted over time.

Speed needs a successful answer from the lab for the phone and the desktop. Both are requested together and the wait is limited, so the rest of the analysis can continue. If both answers fail, performance is left empty and the report says it was unavailable. It is not stored as zero, and a failed attempt is not cached as a finished speed test.

A later run can succeed. Content, cache, the network and the lab itself all change the result. Compare two runs made under similar conditions, and read the individual findings, not only the headline number.

Problems are the concrete findings, shown two per row, with the evidence from the check. Files lists what the page loaded. Images lists the pictures the check could see, with their size and dimensions. Advice is an accordion: a short title, a longer explanation, and numbered steps for that site.

Advice is written and stored in the language of the page you had open. An English report does not reuse Bulgarian advice. If there is nothing to add, the advice tab says so instead of inventing a problem.

The page, the cache, the network between the lab and your host, and the lab itself are not frozen. A cached homepage can look faster than the first hit. A large image, a new script or a certificate that is about to expire changes the findings even when you did not touch the design.

Treat each report as a record of one moment. Run again after a real change, and compare the problems, not only the letter. The history on a paid report keeps the earlier runs so you can see the direction.

No. The score summarises automatic checks made from the outside at one moment: headers, the certificate, public files, and how the page loaded. It does not log in, it does not read the database, and it does not try to break in.

It does not replace a manual audit, a penetration test, updates, backups or ordinary maintenance. A green letter with a missing header is still a missing header. Read the problems list.

Anyone with the unique link can see the public summary. The full explanations, the complete advice and the PDF need the right access: a paid order for that analysis, a credit spent on it, or a package that includes the full report. Share the link only with people who should see it.

The PDF follows the report: scores, the screenshots that exist, the problems and the advice in the language of that report. It is a document of that run, not a live dashboard.

An analysis pack buys checks on this website. You spend a credit, you get a report, and you can unlock the full version and the PDF. SitePulse Pro is a different product. It is a one-year license for one WordPress site, and the repair buttons live inside the plugin, not on this website.

Buying ten analyses does not turn on Pro. Buying Pro does not add analysis credits. The pricing page lists them separately. The pack named for ten analyses and the WordPress license are not the same item, even though both can use the word Pro.

Packs are sold by the number of analyses, not by the number of websites. The pricing page shows the current ones: a single analysis, then packs of ten, thirty and fifty. Each is a one-time purchase. The price on that page is the price that will be charged. There is no monthly analysis subscription hidden behind them.

What you buy is the right to run that many full checks and to open the full report and the PDF. Monitoring of uptime is not included. The WordPress license is not included.

A pack adds its analyses to the credits on your account. A logged-in user with credits can spend one credit on a report that is still locked. The credit is used for that report, and the full findings, advice and PDF open for it.

Credits are for analyses you start on this website. An analysis started by the connected plugin does not take a credit. It still respects the account limit and a hard cap of six plugin analyses per hour, so a schedule cannot run away.

Checkout is in demo mode. It does not charge a real card. Use the test number shown on the payment form, 4242 4242 4242 4242, with any future month and a three-digit code. The form behaves like a real card anyway: only digits, grouped, a real length, a valid date and a name without numbers. Extra digits past a real card length are refused.

The full card number and the security code are not stored. A successful demo payment still creates the order, adds the credits or issues the Pro license, exactly as a live payment will later.

No. An analysis pack pays for checks and for the full report of those checks. It does not start uptime monitoring, and it does not switch on a WordPress Pro license. If a package lists monitoring, that will be written on the pricing page. Today the public packs do not.

The plugin can run the analysis on a daily or weekly schedule. That is a repeated report, not a minute-by-minute uptime monitor.

The locked report opens the full problem list, the longer advice, and the PDF. The free view stays short on purpose. Paying once for that analysis, or spending one credit, sets that report as unlocked. A package that includes the full report does the same for the checks it covers.

The public link still exists. People without access see the short version. People with access, including the connected plugin, see the full one.

No. A check started by the plugin on a connected site does not subtract a credit. The connection is enough for the plugin to show the full report. The account limit still applies, and there is a hard cap of six such analyses per user per hour.

Credits remain for checks you start here, and for unlocking a report that was made without a credit. The two counters are separate.

Yes, if you are allowed to ask for the check. Paste the public address. Do not put private URLs, secret tokens, passwords or anything that should not be in a report link.

For a client's WordPress, the Pro license is for one site. The first connected site that opens the plugin with your account claims that license. A second site is refused until the license is for that host. Buy a separate year for a separate site.

Register with an email and a password. The site is in Bulgarian, English, German, French, Spanish, Italian, Romanian, Polish, Russian, Serbian, Greek and Turkish. An address without a language prefix is Bulgarian. English is under /en/, and the other languages use their own prefix. The prefix in the address wins over a saved choice.

The language of the page is also the language of the advice stored for a report started there. Change language before you start if you want the advice in that language.

Add the site under Websites and create a connection code. The screen calls it the code for Pro. Copy that code into the SitePulse plugin on the WordPress site, in the connection step. The same account that bought Pro should be the account that creates the code.

There is no separate license-key field in the plugin. Opening the plugin with a valid code is what binds the license to that host. The account page lists the license, masked, after the purchase.

The account stores your email, the language, the credits, the orders and the sites you added. A report stores the public address and the measurements, findings and advice from that run. Card numbers and security codes are not stored. WordPress passwords, salts and secret keys are not sent by the plugin.

The connection uses a code from your account, not your WordPress password. Read the privacy policy for retention and for how to complain to the Bulgarian commission for personal data protection.

Use the deletion button in Account, or write through the contact page and name the email on the account. That records a request. It does not wipe the account the moment you click. Orders and reports may need to be kept for the time the privacy policy describes.

Do not send a password or a card number in the message.

Use the contact page. If the question is about a report or a license, include the account email and the report link or the site address. That is enough to find the order.

Do not send passwords, connection codes, or card data. The operator of this site answers through that page. Company registration details are not invented on the site.

Yes for a public check. You can start an analysis and open the short report from its link without registering. An account is what holds credits, past reports, the connection code and a Pro license.

Buying, spending a credit, and generating the code for the plugin all ask you to sign in. A guest who opens the Pro checkout is sent to sign in first, and then brought back.

It is the WordPress plugin named SitePulse. You install it from the zip on this website, or later from the update WordPress offers. It needs WordPress 6.0 and PHP 7.4. The menu is SitePulse. The screen uses the same light colours as this website and the full width of the WordPress content area.

The free plugin connects the site and shows the report, the health and the activity inside WordPress. Pro adds the repair tab. The plugin does not send your password, and it does not profile PHP hooks or outside requests the way a debugging plugin would.

Download sitepulse.zip from the WordPress page on this site. In WordPress open Plugins, Add New, Upload, and activate SitePulse. The folder is sitepulse. After that, WordPress asks this website for new versions. When a newer version is published, it shows under Dashboard, Updates. Open Check again if the plugins list still shows the old version: that list remembers the previous check for about an hour.

The plugins screen itself does not invent an update. The update row appears after WordPress has compared the installed version with the version published here.

In the plugin, paste the code from Websites on this site. When the code is accepted, the welcome steps are skipped and you land on the report. The plugin then asks this website whether Pro is active for that host.

The first site that opens the plugin with a free license binds it. The host is stored without www. Another site gets a clear refusal. There is nothing else to paste: no license string, no extra key.

After the connection, the Report tab shows the scores, the problems and the advice for that site, in the language of the analysis. You can start a check from the plugin. You can set it to off, every day, or every week. The result stays on that screen, with a short activity list.

The Pro tab, if you have not bought the license, shows the price and a link to buy it here. It does not run repairs.

SitePulse Pro costs 99.99 euro per year and is valid for one site. You buy it on this website, on the pricing page or the WordPress page, while signed in to the same account you will connect. The license lasts one year from the purchase.

It is not an analysis pack. It does not add credits. It unlocks the repair tab in the plugin for the one host it is bound to. A second website needs its own year.

Buy it from the pricing page or from the WordPress page, with the button for SitePulse Pro. After payment you return to the account. The account lists the license, with the key masked, the host once it is bound, and the expiry.

In WordPress the license is the Pro tab and the line at the top of SitePulse. When it is active, the plugins list can show the name SitePulse Pro and a note that Pro is on for this site. If the site was connected before the purchase, open SitePulse again so it asks for the license.

Nothing starts on the first click. Every repair button opens a window that says, in plain sentences, what that button will change: which options, which file, which images, which cache plugin. The button that actually does the work is inside that window. Cancel closes it and changes nothing.

After you confirm, a second window stays open and writes each step as it happens: the time, the kind of change, and the file or setting. You can close it when the run finishes. An install reloads the page so the card shows the new state.

It checks whether the https address of the site answers. If WordPress home and siteurl are already https, it writes that nothing was changed. If they are still http and the https address answers with a normal success or redirect, both options are switched to https and the old and new values are listed.

If https does not answer, the addresses stay as they are and the window says why. It does not force a certificate into existence. The certificate still has to be valid on the host.

The button adds one file, wp-content/mu-plugins/sitepulse-headers.php. WordPress loads mu-plugins on its own, on nginx and on Apache or LiteSpeed, so this does not depend on an .htaccess file. The file sends three headers: X-Content-Type-Options nosniff, X-Frame-Options SAMEORIGIN, and a strict referrer policy.

If the file is already identical, it is left untouched. The window lists the file and each header it added. Removing the plugin later does not delete that file by itself. You can remove the mu-plugin file if you want the headers gone.

The button walks JPEG and PNG attachments one by one. A picture wider than 1920 pixels is scaled down to 1920. The new file is written beside the original and compared. The original is replaced only when the new file is smaller. If the new file would be equal or larger, the original stays and the window says it was left as it is.

A previous run that made files larger can be tried again. This time a bigger file is not saved. PNG files are compressed as PNG. The attachment address stays the same, so links in the content do not break. The window shows the real size before and after for every file that actually shrank.

Pro can also write a smaller WebP or AVIF file next to the original. The address in the content stays the JPEG or PNG. A browser that understands the extra file receives it through a picture element. Everyone else still gets the original.

Pro lists four free cache plugins from WordPress.org: LiteSpeed Cache, WP Super Cache, W3 Total Cache and WP Fastest Cache. Each card has the icon, the name, a short line, the author, and a link to the plugin page. If it is missing, the button downloads it from WordPress.org into wp-content/plugins and activates it. If it is installed but off, the button only activates it.

The two setting buttons, cache and minify, appear only on the active plugin that SitePulse will configure. They turn on that plugin's own page cache, browser cache, and CSS and JS minify, using that plugin's settings. If no cache plugin is active, the step says so and changes nothing. Another plugin is not touched.

Yes. On the report screen choose Off, Every day, or Every week. WordPress cron then starts a check and puts the result on the same screen, with the health and the activity. The first run is about an hour after you save, then at the interval you chose.

A scheduled check does not spend a credit. It still stops if the account is over its analysis limit, and it still stops after six plugin analyses in an hour. The schedule analyses the public homepage. It does not run the Pro repair buttons by itself.

It does not send WordPress passwords, salts or secret keys. It does not let an outside model run code on the site. Each repair is a named action from a fixed list, and it starts only after you confirm the window.

It does not install a paid plugin, it does not edit your theme, and it does not delete posts or pages. It does not retry payment, order or email tasks. Files outside a short named list are reported and left in place. If a step cannot be done, the window says it was skipped and why.