the pages themselves seem fast to load, its waiting for a response from the server that is taking time, so M3ta7h3ad's idea is pretty good one doing a traceroute to see where its slow.
Tracing route to microphoto.co.uk [192.254.235.203]
over a maximum of 30 hops:
1 71 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 23 ms 23 ms 22 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184
]
3 23 ms 27 ms 22 ms link-a-central10.pcl-gw01.plus.net [212.159.2.16
8]
4 23 ms 23 ms 22 ms 200.core.access.plus.net [212.159.0.200]
5 26 ms 26 ms 25 ms ae2.pcl-cr02.plus.net [195.166.129.7]
6 24 ms 23 ms 24 ms ae1.ptw-cr02.plus.net [195.166.129.2]
7 23 ms 24 ms 22 ms 10gigabitethernet5-1.core1.lon1.he.net [5.57.80.
128]
8 104 ms 97 ms 100 ms 10gigabitethernet10-4.core1.nyc4.he.net [72.52.9
2.241]
9 118 ms 107 ms 149 ms 100gigabitethernet7-2.core1.chi1.he.net [184.105
.223.161]
10 145 ms 136 ms 139 ms 10gigabitethernet4-1.core1.den1.he.net [72.52.92
.234]
11 156 ms 148 ms 157 ms 10gigabitethernet4-2.core1.slc1.he.net [184.105.
222.154]
12 159 ms 158 ms 191 ms ace-data-centers-inc.10gigabitethernet1-4.core1.
slc1.he.net [66.160.133.118]
13 179 ms 148 ms 148 ms rtr-b.unifiedlayer.com [199.58.199.118]
14 149 ms 149 ms 152 ms 192.254.235.203
Trace complete.
Tracing route to www.google.co.uk [173.194.78.94]
over a maximum of 30 hops:
1 26 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 32 ms 22 ms 23 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184
]
3 23 ms 23 ms 25 ms link-b-central10.pcl-gw02.plus.net [212.159.2.17
0]
4 46 ms 22 ms 22 ms 202.core.access.plus.net [212.159.0.202]
5 30 ms 22 ms 23 ms ae1.ptw-cr02.plus.net [195.166.129.2]
6 39 ms 22 ms 23 ms 72.14.223.32
7 23 ms 23 ms 23 ms 209.85.252.188
8 23 ms 24 ms 22 ms 209.85.253.92
9 53 ms 28 ms 28 ms 72.14.242.166
10 28 ms 36 ms 29 ms 209.85.252.83
11 * * * Request timed out.
12 29 ms 35 ms 29 ms wg-in-f94.1e100.net [173.194.78.94]
Trace complete.
Tracing route to www.tekforums.net [217.160.114.99]
over a maximum of 30 hops:
1 59 ms 99 ms 100 ms dsldevice.lan [192.168.1.254]
2 24 ms 24 ms 22 ms lo0-central10.pcl-ag03.plus.net [195.166.128.184
]
3 25 ms 25 ms 49 ms link-a-central10.pcl-gw01.plus.net [212.159.2.16
8]
4 43 ms 23 ms 70 ms 200.core.access.plus.net [212.159.0.200]
5 23 ms 25 ms 26 ms ae1.ptw-cr01.plus.net [195.166.129.0]
6 23 ms 23 ms 31 ms linx.bb-c.the.lon.gb.oneandone.net [195.66.224.9
8]
7 40 ms 36 ms 36 ms te-1-3.bb-c.bap.rhr.de.oneandone.net [212.227.12
0.49]
8 46 ms 38 ms 38 ms ae-4.bb-d.bs.kae.de.oneandone.net [212.227.122.7
]
9 41 ms 62 ms 38 ms ae-2.gw-dista-a.bs.kae.de.oneandone.net [212.227
.121.216]
10 38 ms 82 ms 38 ms vl-999.gw-ps11.bs.kae.de.oneandone.net [212.227.
125.13]
11 38 ms 37 ms 44 ms kundenserver.de [217.160.114.99]
Trace complete.
Compared to google and tek, the path to your host does seem slower, but not considerably enough to affect the page loading, its probably a combination of factors. I'd definitely talk to your host again.