FAQ / Before the inspection
A few things
to know.
What I test, how I approach your live website and what happens after the report.
Who checks my website?
I’m Ben Frost. I carry out the inspection and write the report. I use technical tools alongside manual testing, then explain what I found, why it matters and what to look at first.
How is Website Check related to Iceni Web?
Iceni Web is where I design and build websites for small businesses. Website Check is the inspection service: I test the agreed public pages and customer journeys, then write up the findings. You can take the report to your own developer. Any repair work needs a separate scope and agreement.
Is this an SEO audit?
The check focuses on whether your website works properly for customers. Keyword rankings, backlink analysis and ongoing SEO campaigns are outside its scope.
Is it an automated scan?
I use technical tools, but I also work through the agreed customer journeys myself. The report explains what I found in plain English and records checks that passed too.
Can I give the report to my developer?
Yes. The report is designed to help you and your existing developer prioritise fixes. There is no obligation to use Website Check for repairs.
Is every page checked?
The inspection uses representative pages, templates and important customer journeys. The final scope will be agreed before work starts.
Is this a security audit?
No. I review publicly observable security basics, such as HTTPS and browser warnings. Penetration testing, exploitation and invasive scanning are outside the standard service.
Is this an accessibility audit?
No. I highlight obvious barriers such as keyboard access, missing labels and contrast problems. This is not a formal accessibility audit or WCAG certification.
Do you fix the issues as well?
Repairs are separate from the inspection. You can fix issues yourself, give the report to your existing developer or ask whether I can help. Any repair work needs its own scope and agreement; there is no obligation to use Website Check.
What types of websites can you check?
Public business websites, including brochure sites and representative enquiry or booking journeys. I agree the pages, templates, integrations and exclusions with you first. Private account areas and end-to-end ecommerce transactions are outside the standard check.
Do you check WordPress?
Yes. I inspect the public website and visible customer journeys, including observable problems with themes, plugins and integrations. The standard check does not require WordPress admin access or include updates and repairs.
Do you check Shopify?
Yes, for agreed public pages and customer journeys. Checkout, payment and other ecommerce-specific testing need separately agreed scope. A dedicated ecommerce package is planned for later and is not currently available.
Will you submit my contact forms?
Potentially, with your authority and agreement on where test messages will go. Submissions are clearly labelled as tests. I don’t use real customer details or send test enquiries without permission.
Will this affect my live website?
The check follows ordinary customer activity on agreed public pages. I don’t change your website or perform invasive tests. Browsing may still trigger normal analytics or integrations, and authorised test forms may create messages, so I agree those activities with you first.
Do I need to give you my website login?
No login is needed for the standard inspection of public pages. Do not send passwords, payment details or sensitive customer information. Any work requiring account access would need a separate agreement.
How long does it take?
Usually within one week of agreeing the scope.
