Skip to content

Your website, fast and secure.

Federico Medinilla

I review each site from the outside, the way any visitor sees it, and deliver a written, color-coded report.

Ask for your free diagnosis
  • No access or installation
  • 45 minutes of work
  • Public information only

Real diagnosis · institution

38 applicable checks

  • 4 Fix now
  • 7 Review
  • 11 Optional improvement
  • 8 Fine
  • 8 Not verified
See the report

What I check from outside

The outside diagnosis uses only what the site shows any visitor: the server responses, the domain, the email setup and the page itself.

It needs no access or installation. The report says what is fine and what should be fixed, and every line ends up with its color and its evidence.

  • 39 checks
  • 45 minutes
  • Public tools

Without written authorization from whoever is responsible for the site, the review is limited to what is public. Accessing a computer system without permission is a crime in Argentina (article 153 bis of the Criminal Code).

  1. Secure connection and expiry dates. The padlock grade, the protocols, and when the security certificate and the domain expire.
  2. Browser protections. The instructions the server gives the browser so the site cannot be turned against its visitors.
  3. Versions on display. Which system, page builder and plugins are visible from outside, and whether they have publicly known flaws.
  4. Doors left open. Private files, forgotten copies of the site, folders that list their contents and old access points still active.
  5. Domain email. Whether the domain can be used to send fake email and whether it sits on spam blocklists.
  6. Speed. How long the server takes to respond, how heavy the page is and how it loads on a phone.
  7. How Google and social networks see it. Whether it can be indexed, how it shows in results and how the link looks when shared.
  8. Accessibility and contact. Contrast, image descriptions, keyboard use and whether direct contact is easy to find.

What a report looks like

This is a real outside diagnosis of an institution’s site, with the name removed. It reads top to bottom: the urgent part first, and at the end what is fine or could not be verified. The groups open and close.

Outside diagnosis · institution · 2026

38 applicable checks

Fix now 4
  • No basic browser protections. Grade F, the lowest: 5 of 12 tests fail, and instructions that stop the site being turned against its visitors are missing.
  • Domain email not fully protected. Some of the domain email’s protections are missing and should be completed.
  • Updates behind. Some parts of the site are not up to date.
  • Domain on a spam blocklist. Emails that link to the domain may end up in the spam folder.
Review 7
  • Versions on display. The site shows which versions it runs, something worth hiding.
  • Admin details on show. The site shows details of its admin panel that should be hidden.
  • Internal names visible. Old certificates, which are public, reveal internal system names; none of the subdomains found can be taken over by someone else.
  • An access route to restrict. An old access route is still open and should be closed or limited.
  • Old site copies: two unconfirmed. None of nine usual locations holds an old copy of the site; two more could not be checked.
  • No page cache. The site rebuilds every page on each visit, so it slows down at traffic peaks.
  • First response slightly slow. Across three runs, the server took a median of 0.82 seconds to start responding; the recommended maximum is 0.8.
Optional improvement 11
  • Server version visible. The server announces its name and version, a detail better kept hidden.
  • Three links without the padlock. Three links on the home page lead to pages without a secure connection.
  • Two sitemaps. Google is offered two sitemaps; one of them could not be read.
  • Preferred web address, partly checked. The home page correctly tells Google its preferred web address; an inner page went unverified.
  • Generic home page title. The home page title is generic and its description is shorter than recommended.
  • Home page without a main heading. The home page has no main heading, only subheadings, which is one reason it appears worse in Google results.
  • Confusing preview when shared. Two previews compete when the link is shared; neither uses the recommended size.
  • Google data not validated. The home page describes the institution in a single block of data for search engines; its validity was not tested.
  • One broken internal link. One internal link on the home page ends in an error and others take a detour.
  • Images without descriptions. One in four home page images has no description for screen readers.
  • Language set, generic title. The page correctly declares Spanish as its language; the issue is the generic title, already noted above.
Fine 8
  • Secure connection well configured. Grade A and current protocols, so browsers show no security warnings.
  • Server folders closed. Four server folders were tested and none shows its contents to outsiders.
  • Same content for everyone. Desktop, Google and mobile get a page of the same size with no redirects, so a typical intrusion sign is absent.
  • No dangerous redirects. No link on the home page can be abused to redirect visitors to another site.
  • Always reaches the secure version. Typing the address without https or www leads, in one step, to the secure version.
  • Compressed page, modern protocol. The home page is sent compressed over a modern protocol, which speeds up loading.
  • Google can show the site. Nothing stops Google from showing the site; only the admin panel is blocked.
  • Direct WhatsApp link on the home page. The home page links to WhatsApp with an inquiry message already written.
Not verified 8
  • Private files: three unconfirmed. Eleven of 14 sensitive files are not exposed; the server blocked checking three.
  • Mobile speed not measured. Speed on phones was not measured: Google’s tool returned no result.
  • Domain expiry unconfirmed. The domain’s expiry date was not seen: no automated lookup is available, so it needs a manual check.
  • Total weight not measured. Google’s tool returned no result, so total page weight went unmeasured.
  • Google results not checked. Google was not searched for pages under the domain that its owner never published; that needs a browser.
  • Readability and keyboard unmeasured. Text contrast and keyboard use were not measured: they need a browser test.
  • Zoomed use not measured. The page was not tested at 200% zoom: that needs a browser test.
  • Main form not checked. The form’s fields and buttons were not checked; they need a browser test.

Checks that do not apply to a site are left out of the count; in this case, 1 of 39. A green line always has its evidence kept, and whatever could not be verified stays gray.

The complete analysis

From outside, only part of the users, files, database and server can be seen, and none of the backups.

Comparison between what the outside diagnosis sees and what the complete analysis adds.
What is checked From outside · free Complete analysis
Secure connection and domain Partly visible from outside: Padlock, protocols and expiry dates Checked by the complete analysis: Who controls the domain and DNS accounts
Backups Not visible from outside Checked by the complete analysis: Whether they include the database, whether one is kept off the host, and whether they can restore the site
Email and forms Partly visible from outside: Domain protection against fake email Checked by the complete analysis: Hidden forwards and whether forms reach their inbox
Google, reputation and shared links Partly visible from outside: Indexing, link previews and risk lists Checked by the complete analysis: Hidden links in the content and redirects only Google sees
Speed Partly visible from outside: Response time, page weight and phone loading Checked by the complete analysis: What slows it: PHP, cache, database and slow queries
Components Partly visible from outside: What the code shows, with versions Checked by the complete analysis: Every installed component: known flaws, abandonment and licenses
Security settings Partly visible from outside: Browser protections and old access points left open Checked by the complete analysis: Whether anyone can sign up, the code editor, permissions and configuration
Users and two-factor login Partly visible from outside: Whether the user list is exposed Checked by the complete analysis: Who is an administrator, shared accounts and two-factor login
Files and database Partly visible from outside: Private files or old site copies exposed Checked by the complete analysis: Whether the system files match the originals and whether there is hidden code
Server and hosting Partly visible from outside: What the server announces about itself Checked by the complete analysis: PHP version, logs, scheduled tasks and disk space
Server access and third parties Not visible from outside Checked by the complete analysis: FTP and SSH accounts, service keys and former agencies

What the complete analysis adds

  • I check there is a full backup that includes the database and, if there is none, I make one first. Then I restore it on a test subdomain, never on the live site.
  • I compare the system files with the originals and look for hidden code in files, database and scheduled tasks, which the outside diagnosis cannot reach.
  • I deliver the list of everyone who can get into the site and the server: administrators, FTP and SSH accounts and access left to former agencies. It also shows who uses two-factor login.
  • Besides measuring how long the site takes to load, I look for what slows it: the PHP version, the cache, the database and slow queries.
  • I delete nothing: I log the findings with the same colors and finish with a plan for the Tune-up. If a sign of intrusion shows up, I stop the analysis, preserve the evidence and move to a Rescue.

USD 100

  • 1 to 2 hours with access
  • deducted from the Tune-up

It needs written authorization from whoever has authority over the site, the hosting and the domain, and an administrator account in my name that the institution removes at the end. If the site has no backup that can restore it, making one may take an extra work session.

Ask for the complete analysis

After the analysis

Three ways to continue, depending on what the report shows. Launch prices, in US dollars.

  • Tune-up

    USD 300

    • list price 400
    • one-off
    • 4 to 8 hours of work

    I fix the red and yellow lines of the report following a plan the institution approves first, with a tested backup and the same measurement before and after. Blue lines are added on request.

  • Guard

    USD 60

    • a month
    • list price 80
    • hosting not included
    • business-hours response

    Monthly maintenance so that what is green stays green: updates with a backup first, weekly checks, a monthly restore test and a monthly report. If there is an attack, one standard clean-up a year is included, within a cap on hours set at sign-up.

  • Rescue

    USD 300

    • list price 400
    • up to 8 hours

    For a site already hacked: containment, clean-up, an orderly change of passwords and access keys, and verification. The first month of Guard is included. Anything past 8 hours is billed at USD 40 an hour, with a cap agreed in advance.

Launch prices for the first five clients or until 31 December 2026, whichever comes first; Guard keeps that price for as long as it stays active. Shops on WooCommerce or Tiendanube: 50% more on the Tune-up and Guard. In Argentina, paid in pesos at the official rate on the day of the quote.

How I work

I spent two years rebuilding WordPress and Elementor sites for a consultancy, in teams of more than five people, and before that I built more than fifty sites for three agencies. I know where they break.

For this service I built my own method of 146 checks. Each one states where to look, what to look for, what to do if it fails and what not to touch. The report belongs to the institution, with no strings attached.

On this very site, Mozilla’s header test gives the top grade and there are no third-party scripts. Measured on 3 October 2026.

Four fixed rules

  1. I touch nothing before restoring a full backup in a test environment.
  2. Passwords never travel by WhatsApp or email: the institution creates an account in my name and removes it when the job ends. Under Guard that account stays active, with two-factor login.
  3. I measure three times with the same tool, before and after, and report the median.
  4. Without written authorization, I only review what any visitor can see.

Frequently asked questions

Do I have to give you the site password?

No. The outside diagnosis needs no account at all. For any work with access, the institution creates an administrator account in my name and removes it at the end; under Guard that account stays active, with two-factor login.

What is the difference between the diagnosis and the complete analysis?

The outside diagnosis is free and looks at what any visitor sees. The complete analysis costs USD 100, needs authorized access and covers users, backups, files, database and server.

Does it work if the site is on Wix, Squarespace or Shopify?

Yes, with a different scope than on WordPress. The outside diagnosis is the same, minus the checks specific to WordPress and the server; with access I review the account, the domain, the email setup, the speed and the installed apps. Files and servers are run by the platform.

What if the site is attacked while on Guard?

Guard includes one standard clean-up a year, within a cap on hours set at sign-up. If the case needs a rebuild from a backup or work with the host, it is billed by the hour with a cap agreed in advance.

Is there a guarantee the site will not be attacked again?

Security has no guarantees. The Tune-up fixes what the approved plan covers and measures it again at the end. With Guard, the monitor flags downtime within minutes and alerts are reviewed every week; response is during business hours, Monday to Friday, 9 am to 6 pm Buenos Aires time.

How long does each step take?

The outside diagnosis, about 45 minutes of work. The complete analysis, one or two hours with access. The Tune-up, four to eight hours of work, in a low-traffic window agreed in advance. A Rescue depends on how compromised the site is and is estimated after containment.

Which currency?

US dollars. In Argentina, pesos at the official rate on the day of the quote. Guard is paid month by month.

What if I stop after the diagnosis?

The report belongs to the institution, with no strings attached, and it can be shared with anyone.

Ask for your free diagnosis

The site’s address is enough. Whether to continue is decided with the report in hand.

The Tune-up is paid half up front and half on delivery, with the before-and-after numbers in view. Guard, month by month.

Buenos Aires · I reply the same day · español / English

New message

To: Federico Medinilla

Subject: Free diagnosis of my website

Two or three lines is plenty. Screenshots or an example can come later.

It comes straight to me. No mailing list.