to emulate the Refresh HTTP header, and as such can also be sent as a header by an HTTP web server. Although Refresh is not part of the HTTP standard, it is supported by all common browsers. HTTP Header example of a redirect to https://example.com/ after 5 seconds: Refresh: 5; url=https://www.example.com/ Alternatives exist for both uses of meta refresh. For redirection An alternative is to send an HTTP redirection status code, such as HTTP 301 or 302. It is the preferred way to redirect a user agent to a different page. This can be achieved by a special rule in the Web server or by means of a simple script on the Web server. JavaScript is another alternative, but not recommended, because users might have disabled JavaScript in their browsers. The simplest way of JavaScript redirect using the onload property of the body tag: <body onload="window.location = 'http://example.com/'"> <!-- Your content here --> </body> For refresh An alternative method is to provide an interaction device, such as a button, to let the user choose when to refresh the content. Another option is using a technique such as Ajax to update (parts of) the Web site without the need for a complete page refresh, but this would also require that the user enable JavaScript in their browser. You can refresh a web page using JavaScript location.reload method. This code can be called automatically upon an event or simply when the user clicks on a link. If you want to refresh a web page using a mouse click, then you can use the following code :<a href="javascript:location.reload(true)">Refresh this Page</a> References External links W3C Web Content Accessibility Guidelines (1.0): Ensure user control of time-sensitive content changes meta refresh deprecated by W3C Use standard redirects: don't break the back button! H76: Using meta refresh to create an instant client-side redirect JavaScript Page Refresh HTML Hypertext Transfer Protocol headers