What is the SiteScanner?
SiteScanner is a free tool that tests your site for speed, SSL verification, and security.
What is a HAR file and why should I use it?
An HTTP Archive (HAR) file is a common format for recording HTTP tracing information, or logging a web browser’s interaction with a site. The data is stored as a JSON document and extracting meaning from the low-level data is not always easy. With practice, the HAR file can quickly help you identify the key performance problems with a website.
What information does a HAR file include?
You can expect a HAR file to include a breakdown of how long it takes a browser to retrieve several key components of a website:
- How long it takes to fetch DNS information;
- How long each object takes to be requested;
- How long it takes to connect to the server;
- How long it takes to transfer assets from the server to the browser of each object
How do I read/understand the contents of a HAR file?
Resources are available across the web to help you read and understand the HAR file’s contents. We’ve covered how to visualize a HAR file on our blog.
We recommend these resources as well:
Why is one site faster (or slower) than another?
There are many factors that can influence one site’s performance compared to another’s.
Why wasn’t WordPress detected on my site?
WordPress may not have been detected because you’re either using a CMS type other than WordPress, or there was a problem with the information listed in the header section of your WordPress site.
WordPress detection is done through builtwith.com. We look for signatures or signs that WordPress gives. Their API looks for fingerprints of each version of a CMS.
Note that results may be slightly delayed. For example, we check things like whether certain files exist and what’s listed in a header. It’s worth mentioning that WordPress exposes this metadata to assist with troubleshooting and we analyze the most recent data available on your site.
When will SiteScanner be able to detect other CMS types like Joomla and Magento?
We’re working hard to add support for a whole range of other popular content management systems. Contact us with your CMS type and we will do our best to prioritize.
What information does SiteScanner verify about my SSL certificate?
SiteScanner checks to see if your site’s SSL certificates are up to date, issued by valid authorities, trusted by end-users’ browsers, and providing a safe environment for visitors.
SiteSacnner currently does not check that the certificate is valid for the domain against which it is checking, but this is a feature we are working on adding.
How do I optimize my site?
Having a faster site not only pleases visitors, it helps to boost your ranking on search engines like Google and Bing too. StackPath offers many ways to do that.
Content caching, load balancing, content compression, and minification are just a few ways the right Content Delivery Network (CDN) can help you optimize your site.
StackPath allows users to take advantage of all these things to speed up their sites while protecting them from security threats.
What are some additional things I can do to increase the speed of my site?
One easy way to optimize your site is to simplify the page's design. It is possible to build your site to include rich content while also achieving optimal response times.
There are several things you’ll want to keep in mind when determining how to decrease page load time on your website, including:
- How to minimize HTTP Requests
- Whether your site contains empty src or href code
- How to add an Expires or Cache-Control header
- How to utilize Gzip components
- Are your stylesheets at the top of your page’s code
- Are scripts located at the bottom of your page’s code
- How to avoid CSS expressions
- How to reduce DNS lookups
- How to avoid redirects
- Are you removing duplicate scripts
- How to configure ETags
- How to make AJAX cacheable
- How to use GET for AJAX requests
- How to reduce the number of DOM elements
- Is your site full of 404s
- How to reduce cookie size
- How to use Cookie-Free Domains for components
- Are you avoiding filters
- Make sure you do not scale images in HTML
- Make sure favicon.ico is small and cacheable