printshop.example

Anyone who finds it can use it as if they were you.

File and line: assets/shop.js, line 88

Once it expires, browsers will show visitors a full-page security warning. Renew it, or turn on auto-renew with your host.

Visitors who type "www" land on an unencrypted page. Send every version of your address to the HTTPS one.

Without this setting, a visitor on public Wi-Fi can be quietly pushed onto an unsafe connection. One response header fixes it.

Part of a secure page is coming in unsecured, so browsers may block those images or drop the padlock.

This header tells browsers which scripts are allowed to run. Without it, an injected script has an easier time running on your pages.

Another site could show your order page inside a hidden frame and trick people into clicking. A header can block framing.

If the site hosting those scripts is ever changed or hacked, your pages will run the new code without noticing.

Anyone can rebuild your readable front-end code from these files. Usually harmless, but it makes your app easier to study for weak spots.

Visitors can browse that folder like a file manager, including customer artwork if any is stored there.

It maps out how your app’s back end works. Hide it or put it behind a login before launch.

When something breaks, visitors see file paths and framework details meant only for you. Show a plain error page instead.

These cookies aren’t marked Secure, so they could travel unencrypted and be read on the way.

If a bad script ever runs on your page, it could grab this cookie and use the visitor’s session.

Your API answers every site that asks, so another site could pull data a signed-in visitor can see. Allow only your own domain.

Mail providers can’t tell which servers may send email as you, so order confirmations are likelier to land in spam.

Scammers can send email that looks like it’s from your shop, and you won’t get reports when they try.

Your order form collects names, emails and addresses, but there’s no privacy page linked from the home page. Many laws and payment providers expect one.

Search engines have to discover your product pages on their own, so some may show up late or not at all.

Visitors clicking "Wedding invitations" and two other links hit a "not found" page.

Screen readers can’t say what those fields are for, and the form is harder for everyone to fill in.

Your phone-size home page downloads about 9 MB of images it shrinks anyway, which slows the page down.