If the browser knows that the tabs.html is a reusable component that does not have changing content, it can cache it very intelligently. Also if someone builds a tabs component and hosts it on foo.com/999/tabs.html (CDN) which you use, your visitors may already have it downloaded and cached.
So I think in the long run, something like this would be a better solution.
Comments
If the browser knows that the tabs.html is a reusable component that does not have changing content, it can cache it very intelligently. Also if someone builds a tabs component and hosts it on foo.com/999/tabs.html (CDN) which you use, your visitors may already have it downloaded and cached.
So I think in the long run, something like this would be a better solution.