It's good to keep in mind certain factors when running these tests due to bandwidth shaping:
1 - time of day (peak/off peak)
2 - "burst" modes (high throughput sustained for short periods, usually 30 sec to 2 minutes, before being turned down. Good for page loads, not good for large file transfers or movies.
3 - upload bandwidth
Initial test (off peak); most of the tests seen here will be enhanced by their providers for short demand.
Test with download shortly after the first test. This gets worse during peak times, especially for Netflix.
You need a decent upload bandwidth in order to take advantage of high download rates as well, as a page load is a two way street. You can effectively kill your browsing experience to zero very easily if you clog your upload bandwidth with large files without using some sort of bandwidth restriction via software.
It's the server you're testing up against, and all the little connections made in between. You're only paying Verizon for access, but your data travels on lines owned by various providers. You'll get different results from different servers, depending on their connection quality or even distance. I wouldn't worry so much about that as long as you're not constantly triple digits.
As an example, my local testing server is in the same city and I get 6ms ping. I just tested against a server in NEW ZEALAND, and got 23ms ping. Then I tested a server in south TEXAS, which measured 182ms ping and I live in the Pacific North West.