Why Is My Website Slow? How to Find Out With Free Tools

Herramientas SEO y web gratis
Sep
27

Why Is My Website Slow? How to Find Out With Free Tools

09/27/2026 9:30 AM por Justin Zwick en Site speed


Why is my website slow diagnosis showing page size, server response time and heavy images

If you're asking "why is my website slow?", the answer is usually one of a few common causes, and free tools can tell you which one in a few minutes.

A slow website loses visitors. People don't wait long for a page that seems stuck, especially on a phone. Speed also matters to search engines as part of how they judge page experience. The good news is that most slow sites are slow for a handful of common reasons, and you can diagnose them with free tools on Free Micro Apps.

Why is my website slow when pages keep getting heavier?

Part of the answer is that pages have grown. The HTTP Archive Web Almanac 2024 found that the median mobile page weighs about 2,311 KB, that the median mobile page grew by 357% over ten years, and that 92% of pages load third-party resources. The same report found that text compression was used correctly on only 70% of desktop homepages, so turning on compression is often a quick win.

Step 1: Measure before you change anything

Pick two or three important pages, such as your homepage, a top product or service page and a popular article. Test each one so you have a baseline to compare against later.

Write down the results. Test more than once, since results vary a little from run to run.

Step 2: Check the page size

Page weight is one of the simplest and most telling numbers. A page that downloads several megabytes is going to be slow on a mobile connection no matter what else you do.

If your page is heavy, the next question is: heavy with what? Usually it's one of these:

Images

Images are the most common cause of heavy pages. Typical problems:

  • Photos uploaded straight from a camera or phone, at full resolution, displayed at a fraction of that size.
  • No compression. Many images can be made much smaller without visible quality loss.
  • The wrong format. Photos saved as PNG instead of JPEG or WebP, for example.

Fixes: resize images to the largest size they're actually displayed at, compress them, and use modern formats where your platform supports them. Many platforms and plugins can do this automatically for new uploads.

As a bonus, photos often carry hidden metadata such as camera details and sometimes location. The EXIF Data Viewer shows what's embedded, and the EXIF Data Remover strips it, which is good for privacy and trims a little weight.

Video

Videos embedded directly on a page can be very heavy. Using a video platform's embed, and making sure videos don't autoplay or preload unnecessarily, usually helps.

Fonts

Each custom font and weight is another file to download. Using fewer font families and weights is an easy saving.

Step 3: Look at scripts and third-party code

Many slow sites aren't slow because of their own content but because of everything bolted on: chat widgets, social media embeds, multiple analytics tools, ad scripts, popups, sliders and plugins.

To investigate:

  • Use View Page Source to see what's loaded on the page. Look for scripts from many different domains.
  • Ask, for each one: do we still use this? Does it need to be on every page?

Removing a single unused plugin or widget can make a bigger difference than hours of fine-tuning.

The Code to Text Ratio Checker is another rough signal. A very low ratio means the page has lots of code relative to its visible content, which sometimes points to bloat.

Step 4: Check the server

If the page is light but still slow to start loading, the server may be the bottleneck.

Signs of a server problem include a long wait before anything appears, slow performance at busy times, or consistently slow responses even for simple pages. Possible fixes include enabling caching, using a content delivery network (CDN), upgrading your hosting plan or moving to a better host.

Step 5: Fix in the right order

Work from the biggest, easiest wins to the smallest:

  1. Compress and resize images. Usually the biggest win for the least effort.
  2. Remove unused plugins, widgets and scripts.
  3. Enable caching through your platform, a plugin or your host.
  4. Reduce fonts to what you actually need.
  5. Consider a CDN if visitors come from many regions.
  6. Look at hosting if the server is slow even after the above.

Step 6: Measure again

Re-test the same pages with the same tools and compare against your baseline. If a change didn't help, undo it or move on. Keep notes, because speed tends to drift over time as new content and plugins are added.

Don't forget mobile

Test on mobile results, not just desktop. Mobile devices are often slower and on slower connections, so problems show up more clearly. The Screen Resolution Simulator also helps you see how your layout behaves at different screen sizes.

A quick summary

  • Measure first and keep a baseline
  • Check page size, and find what's heavy
  • Fix images first
  • Remove unnecessary scripts and plugins
  • Check the server and caching
  • Re-measure and keep notes

Most sites get noticeably faster with just the first two or three fixes. If you'd like help, contact us.

Key takeaways

  • Measure first: page size, response time and number of requests
  • Images are usually the biggest and easiest fix
  • Turn on text compression on your server
  • Remove third-party scripts you don't need
  • Re-test after every change

Frequently asked questions

What's the most common reason a website is slow?

Oversized images are one of the most frequent causes, followed by slow server response and too many third-party scripts.

Does hosting affect website speed?

Yes. Slow server response time often points to hosting or backend issues, especially on cheap shared hosting.

How do I check my page size?

Use a free page size checker to see how large the page is and what's adding weight.

What is a good load time?

Faster is better. Google's Core Web Vitals treat a Largest Contentful Paint of 2.5 seconds or less as good.

Will a caching plugin fix everything?

Caching helps response time, but it won't fix oversized images or heavy scripts on its own.





Free Micro Apps is a Justin Zwick project. See all projects. Last updated .