This can be useful. Often, when you finish reading a web page, your mouse pointer is near the bottom of the window, so being able to navigate from the bottom can be handy. However, before you add a history button, there are several important questions to think about:
What does back mean within the context of your web page?
Where do your readers want to go back to?
Where do you want your readers to go?
Are any or all of these likely to match the url in the browser history?
All too often, I find a really great web page from a web search or link that is obviously part 2 or 3 of a larger series. I see a back button, press it thinking that it will take me back to the previous page in the series and end up back at the previous page in my history. I go back to the page I'm interested in, look around and there is no link to an index or the first page in a series. There is a next or forward button, the mirror image of the one I tried, and it goes to the next page in the series. This is probably a bad use of the history feature.
There are excellent uses of the history feature. If you link difficult or unfamiliar words to a glossary, having a back button after each entry in the glossary could make a lot of sense. You may link to the same glossary item from several different places in your site and people are likely to want to go back to the page they were reading after looking up the term.
Once you decide that you do want to implement a history feature, it is very easy to do. All you have to do is link your image to a URL of the form:
Or set an appropriate event to call window.history.back()