Site size reduced, but loading speed didn't improve

[rlopes]

I've reduce my site's size in about 30%, but according to Pingdom, the loading time didn't improve at all (please look at the table below). How's it possible?

April 28 15:45:20 1.99 s 548.5 kB 69 77
April 28 11:15:50 2.02 s 557.3 kB 68 77
April 27 15:21:58 1.98 s 549.1 kB 68 77
April 27 14:37:11 1.76 s 657.0 kB 71 78
April 27 11:17:14 1.40 s 661.8 kB 70 77
April 27 10:50:15 2.02 s 678.8 kB 69 77
April 25 14:42:25 1.10 s 655.8 kB 70 76
April 25 14:41:38 2.09 s 651.6 kB 70 75
April 25 12:16:21 1.45 s 654.1 kB 71 75
April 24 23:14:01 2.02 s 742.9 kB 71 74
April 24 23:02:43 1.92 s 743.1 kB 72 74
April 24 22:57:57 2.10 s 742.9 kB 69 74
April 24 22:50:19 2.01 s 760.1 kB 72 73
April 24 22:41:04 2.24 s 794.5 kB 79 62
April 3 16:38:05 1.33 s 795.8 kB 80 63
April 3 15:08:04 1.50 s 793.2 kB 80 71

[Swanny007]

Try another source like www.webpagetest.org for comparison sake.

[incrediBILL]

Could it be cache?

Are they actually reloading the page?

Try [urivalet.com...] as it will show you all files and associated load times, very useful.

[rocknbil]

Page size or loading time? If there's no change in reported page size, that's a problem with the service. The loading time can be affected by many factors, the primary of which are the number of requests on your page and the server's response time.

[rlopes]

@Swanny007
I checked webpagetest and it reports a loading time of more than 4 secs, which is the double of what I get with Pingdom. The problem is that I don't have it's loading time prior to the site improvements to make a comparison.

@incrediBILL
Seems like they clear the cache on every request.
I'll try urivalet, thanks.

@rocknbill
I know we are talking about two different metrics, but it's something to expect that a 30% reduction in size would have a considerable reduction in the loading time.