There might be specific reasons to do it way you're doing, but it's generally considered bad practice to track pageviews or activity via MySQL. Your two problems now are that pages are cached, and the tracking ability will be severely underpowered. For example, you'll be missing an ability to separate organic vs robot traffic.
It's best to allow an independent, trusted and capable metrics vendor to do that tracking as they do it for a living - and they can provide a rich dataset to explore.
Warning: check your host's TOS
Note that some hosting companies explicitly forbid forms of 'performance tracking' for managed SQL uses in their terms of service (count increment might apply here, since it can alter index information.) Unless you're using InnoDB storage engine, the performance will always be bad because the table is locked for all reads until the update is finished.
Use Google Analytics
There are limitations to GA, but the positives are that:
- CACHING: it bypasses any local caching schemas
- EFFICIENCY: offloads tracking overhead resources onto the client
- PRICE: it's free to use
- FILTER: robot traffic is removed from human activity
- BROWSE: reports can be neatly organized, shared and explored
- WRITE: has virtual page tracking (so your unique Ajax-dynamic page interaction can still be tracked)
- READ: there is an API you can use to retrieve the data; ex: most viewed (see http://www.electrictoolbox.com/google-analytics-api-php-class-most-popular-pages/)