Optimizing Initial Server Response and Unused JavaScript

Hello. Please send a link to website

This usually happen when cms response is slow

What backend do you use?

I am using Baserow

The CMS content is down on the page? If we could somehow lazy load them it could solve it, right?

From what I see you load like 300kB of data. Maybe reduce amount of resources or load less data if possible.

Is there any other way? I can reduce this but I'm thinking what if a project where I can't reduce it.

What would be the solution for that?

Seems like baserow api responses has no caching headers too. Probably we need to allow explicit caching to use strategies like cache/first etc

Not sure what does it mean, but if it improves the performance, please do it.

Though keep in mind even with caching first request will show bad metrics unless you request each page manually before crawler. So fast backend is the best option.

any recommendations?

"what if" is not a great way to think about it, usually the goal is load the minimum amount of data when you server-render, then load more when necessary

depending on the use case there are different answers, but without having a use case there is no point talking about a different solution

yes, we have an issue for something like this https://github.com/webstudio-is/webstudio/issues/4077

all our usages of baserow have been very snappy so far https://webstudio.is/tools/headless-cms-finder

@Bashar generally check how many resources you are loading on the page, you may be having something you don't use and didn't delete

when checking performance you can also make the same request using any 3rd party tool and see how fast the data gets fetched as as baseline for what to expect

I am using as less as possible as you can see in the website. and they're all coming from the same API.

I can't see that from the published website if you have resources you are not using

I doubt your single baserow collection takes much time, should be nothing

Let me send you the view link in your inbox

https://pagespeed.web.dev/analysis/https-www-airdokan-com/4tcvlcdwbf?form_factor=mobile

there is no issue at all

@Bashar Not sure if you knew, but you can use a parameter like exclude to take out fields from the response such as linked records.

For example:
/api/database/rows/table/TABLE_ID/?user_field_names=false&exclude=field_6363

Thanks Ronald. I didn't know that.

You're welcome! I was trying to figure that out as well 😁