Tag Info

New answers tagged

1

When you request a web page, you request more than the web page. You are requesting the HTML file, all images, all CSS files, all JS files, all Font files, etc. Your server will rarely let you request all of those items at once. It will instead limit the number of concurrent requests and ask you to queue up the rest. This isn't a huge deal, but the more ...


0

You should put 'em on your server :-) Reason: 1) It will be faster, even if they have it cached from a prior site that uses Google, it will create the cache 1st time anyway so it would only affect the 1st experience. 2) say the google server goes down and you haven't put them on your server.. then those fonts disappear and are replaced by whatever their ...


2

Loading files from third party servers (google) can slow down loading time since the browser has to make a request to a different machine. Basically loading everything from one domain should be faster than loading files from different webservers. However – chances are that the google font is already in the visitor's cache file. This again would speed things ...


5

Short answer: Google is much faster than you hosting it yourself. Long Answer: Putting it on your own server might seem like a good idea to improve load times. After all, the files are closer to your webpage. But, no. After all, when a user goes to your website, initially they just get some HTML. Here we have references to other files: Images, JS, CSS, and, ...



Top 50 recent answers are included