Why Firebase hosting slow to load static file? - firebase

I'm using Firebase hosting to store static files. I made a test on pingdom and the files are slow to load compare to others :
They say on Firebase that they are one of the fastest CDNs available. Why I can't get good performance?

Related

In Firebase hosting - what does the "usage" tab means?

I have deployed my site with Firebase using my customed domain.
I checked my db usage and it seems fine (couple of megas) but then I go the hosting section and then the usage tab and see almost 1GB downloads, do you know what do the downloads in the hostage section mean?
It means that almost 1GB of data was downloaded from Firebase Hosting in your project.
If this is higher than you expected, you might want to check for the size of your files. Do you have any images? How big are those? How much data will each client read from Firebase Hosting? How many clients do you have? If you have a few large files that everyone loads, it adds up quickly.

How Can I Make My Google Firebase-Hosted Static Site Faster?

I'm hosting a static website generated by Hugo on Google Firebase. I know Firebase simplifies a lot of things from Google Cloud via its console and default settings. However, I'm hoping to make my site faster, and I was wondering if there was any settings I could change on the larger Google Cloud platform such as increasing the number of places the site deploys from, or using an SSD, or a faster virtual machine etc.
This is for a static website generated by Hugo being hosted on Google Firebase and with a CDN via CloudFlare. I've done plenty of optimization via the typical website optimization stuff, but I was wondering if there was anything I could do on Google Cloud Platform to increase the reach of my site and its speed etc.
Firebase Hosting doesn't have any configurations that tune its runtime behavior, in terms of performance. The only configurations it has are documented here.

Does firebase storage automatically scan for infected files?

I tried googling but I can only find information about Google drive scanning files with file size less than 25MB. Does firebase storage do the same? I'm planning to build an app and want to ensure that users don't upload infected files. I'm checking if I have to implement virus scanning myself.
Cloud Storage isn't concerned with, and will not change the contents of, the data you put in it. You do, however, have an obligation to honor the Google Cloud terms of service.
If you want to scan the files for whatever reason, you have to do that yourself.

Downsides of firebase functions vs firebase hosting

I want to host my static webapp created with Next.js' export function on firebase. The app rebuilds itself to static html when changes in the underlying database are made. Since I can't directly deploy this static pages automatically to firebase hosting, I tend to serve the static files from with.
So, are there any downsides of serving static html content with Express.js inside firebase function compared to using firebase hosting?
Especially with regard to: Pricing, Security and Performance/Speed.
We hosted our site (https://mfy.im) under Firebase hosting, it's generated using nuxt, similar to your next.js. We've compared many other static hosting sites including Netlify, S3, etc. Firebase hosting was the best in performance
Even though Express can serve your static files, it's not recommended. Firebase internally uses Nginx. Nginx is super fast in serving static files and it's multithreaded. In Nginx, its easy to confiture http2, gzip etc. (full http2 support is recently released in Node 10, gzipping files in node js is also not that performant since the node is single threaded)
Other advantages of Firebase hosting is its edge servers, built-in CDN, SSL etc. A copy of your site is deployed on multiple servers all around the world which results in low latency. I've tested Firebase CDN vs CloudFlare, again Firebase was the best
Regarding Pricing, Firebase hosting comes with a free plan of 10GB bandwidth. It should be efficient for small-medium websites. If your bandwidth usage is higher than that you can go for 'Pay as you go'. However, if you're worried about pricing you can combine Firebase hosting with CloudFlare CDN so that CloudFlare will cover most of the bandwidth

Firebase site - Hosted or Storage for site assets?

I have a small firebase project site that I've been working on and is now public and gaining more traction than I thought. I doubt I'll hit Firebase's 10GB hosting transfer cap, but this got me thinking as to whether or not I'd be better served storing my site assets in Firebase Storage, and if that would help at all. I'm a bit new to these cloud service pricing models, so any help would be greatly appreciated. Boiling it down, here are my questions:
I have 20mb of assets currently stored in a /rsc/ directory on my hosted site. Would it lessen my Hosting "Data Transferred" to move these assets to Firebase Storage (Would the data transferred be logged under my Storage quota)?
Yes, if you put the files in Cloud Storage instead those will not be counted against the Firebase Hosting bandwidth limits. However, you will lose out on the global CDN edge-caching and atomic rollout/rollback provided by Firebase Hosting.

Resources