Tag Info

New answers tagged

0

It would be better to do it yourself. You don't want to rely on an API (if it goes down or it gets discontinued). More often than not, relying on external APIs will slow down the load times of your site. As you probably already know, page speed is a ranking factor.


1

I think that you need to host images by yourself. It will be better, and you will be safe (your images always will be yours, but any DB can install hotlink protection).


1

Don't forget that there is also a 50MB limit to the uncompressed sitemap size. If each of your 50,000 pages had 1,000 images and each image entry in your sitemap were 50 bytes, your entire sitemap would end up being about 2GB. Clearly that is too large. Even including about 20 images per page would put you right about at the 50MB limit. I can't find any ...


0

Tumblr is a big website with a ton of images. Any website of that size with that many images is already going to be using a content delivery network (CDN) for the images. When you use a CDN for images, you usually have put them onto a separate subdomain. Tumblr has done so; another indication that they are using a CDN. Because your site is hosted by ...


1

Should I still have dummy, low bandwidth (ie. 1px x 1px) .png files residing on the server under the names img1.png, img2.png, img3.png, even though the redirect means they will never actually be served on the page? No, these would serve no purpose, since your rewrite rules will always intercept requests to those URLs. Your solution, whilst ...


1

So after some trial and error I came up with a working solution that I'm not quite happy with. But at least it works. Since all "real" images are located in /includes/ or subdirectories I simply rewrote the rule for the images. So this location ~* \.(?:gif|jpe?g|png|ico)$ { expires 168h; add_header Pragma public; add_header Cache-Control ...



Top 50 recent answers are included