A quick way to do this is to check the headers for the content. If the script generates the correct content headers you can simply check the Content-Age or Content-MD5 header to see if the content should be re-gotten. If you have access to the script generating the response it would be good to add these if they are not there.
If you cant modify the script, or these headers are not present the second quickest way to do this is to figure out how much of the page is sufficient for a change hash, retrieve that part and generate a hash to see if it changed. In general computing the MD5 on less than 1MB of content is fairly trivial time wise, with larger data taking more time. If the first part of the page has a timestamp or similar you dont need to hash anything beyond this as it will tell you if the content changed.
Of course the third thing is if the page content changes frequently but you are only interested if the formatting, or volume of the content changed (not the content itself) you will need to identify meaningful structure in the page and compare that. This would be true if you had a page that was writing log files, you didnt care about the log files themselves, but you cared if one was added or a new source was added. This is the trickiest to detect by far.