Forum Documentation Showcase Pricing Learn more

Terrible / Non-existent Mobile speeds even on empty page


#1

I am experiencing really bad scores even on empty pages on Mobile. I also tested it practically and the pages take forever to load on mobile, even wi-fi, even without dynamic content.

Considering 65% traffic is mobile for us and Google is now ranking basing on mobile speed, this of great concern. I also see users closing landing pages as they won’t load.

I am on personal plan and dont think its fair to upgrade to pro plan just to get minimum speeds. What can I do objectively otherwise to resolve this issue or is bubble having problems ?

Link.

I created a new app and literally an empty page and even that’s around 40/100 ! Is bubble framework not mobile ready ?


#2

How are you testing your speeds? What location are you testing from?

We have much more complex pages on our site and are they’re typically in the 50-60 percentile of most website speed testings for mobile.

Note - we’re on a dedicated plan so that could be some of it for sure. I suspect Pro is equally as fast. If you’re using the shared cluster then it may be slower.


#3

Heya.

The above test results are fromgoogle insights, and this is how google perceive and rate them. So I consider this is a real test to pass.

I also have opened these pages from Australia and India using 3g,4g and wi-fi. They are slow. Also the desktop speed is clearly great. So I doubt the issue is with testing or location.

50-60 percentile is not enough from ranking and for landing pages but you getting those speeds surprise me. Are you comfortable sharing your product , public link either here or PM me ? So we can think why they do better. A new-app , empty page is not scoring 50 percentile in my testing.


#4

#5

Test Result Link


#6

I suspect it’s materially slower in Australia and India as Bubble’s servers are based in the US. So, that could certainly be another part of it. I feel like I’ve heard similar from other Bubblers in Australia.

Being at 13% seems crazy low though, especially for a nearly blank page.


#7

Those numbers look way wrong to me. Those results say it takes 17 seconds before I can interact on mobile but when I test it on my phone it takes a few seconds. Certainly less than 5.

Additionally, here’s what I’m seeing about our homepage from Pingdom:


#8

If you see the previous link I posted in your result, google also issues 70 Percentile for Desktop. I am speaking about mobile.

Google now considers speed and on mobile for its mobile ranking.

Are you sure these results are not for desktop ? Also why test using other tools if Google is what brings the traffic in ? I will try to test your page on Mobile wi-fi shortly .


#9

Pingdom used a desktop view - it shows an image of the page.

We use the same page for mobile and have pretty much all of the same content. Perhaps your Lighthouse speed test is simply simulating slower connection speeds. Still doesn’t make sense to me though, as I can access our site quickly from my phone.

Perhaps someone with more knowledge that me can chime in to explain what may be going on.


#10

I got same low result from Google insight at 10 instead of 90. It point out that is the cloudfront’s slow download. I don’t know if @Bubble is aware of that new Google reality, as mentioned by @Prashant , will rank your mobile site accordingly.

https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fwww.yoursite.com&tab=mobile

Recommendations

In your report, Lighthouse lists all of the render-blocking links or scripts that it has detected. The goal is to reduce this number.


#11

The numbers were initially better than what I am seeing now. I remember there was some update in the way Google computed these numbers and so most sites have now a relatively lower number for mobile, but seeing it in single digits certainly doesn’t look good.

Here some reference: https://www.searchenginejournal.com/mobile-page-speed-changes/272221/


#12

@Prashant @JohnMark We understand your concerns regarding mobile ranking. It would help if you can share test apps with significantly worse page speed on mobile than desktop. We can then do a deeper dive.


#13

Hi Neerja.

I am happy bubble has responded to look into this.

Here are some links for testing from my site / my tests.

  1. Triviaroo

This site is completely developed on Bubble and you could look at any page here basically. Here is one of our 1,000 landing pages.

I have specifically encountered mobile slow load on this Sales page. And this blank page has literally no contents and scores 14 / 100. You would expect this to be 90 plus and is a google ranking concern.

@sridharan.s home page also scored low but the practical experience unlike mine was not bad. @JohnMark’s what is your site url ?


#14

Thanks for looking into this @neerja - We appreciate it. Here’s a few more sites. Note, I’m seeing the same challenge with every Bubble site I check and across all pages on those sites.

  • bubble.is - 94 on Desktop, 18 on Mobile
  • meetaway.com - 76 on Desktop, 5 on Mobile
  • zeroqode.com - 43 on Desktop, 0 on Mobile
  • viably.co - 94 on Desktop, 20 on Mobile

#15

I’d love a look at mine if you have the time - venddy.com - 51/desktop, 0/mobile


#16

@sridharan.s Thanks for these examples. Our engineering team is reviewing this issue. We will post back with updates.


#17

LearnBook.net, it’s about the same as the rest :frowning:


#18

@Prashant You can see a detailed breakdown of the connection speed, load times and HTTP requests with WebPageTest from different locales over 3G:

Australia https://www.webpagetest.org/result/181223_0G_2963abed4801da568857114c257714f0/1/details/

US https://www.webpagetest.org/result/181223_90_ec61f769ed55ce6657a7e25097277c24/1/details/

I know this doesn’t help directly, but it revealed a couple things: there are 20+ separate Google Font requests that eat up a large chunk of the requested page. Perhaps you can limit the number of different fonts you rely on in your app Style section and stick to 2-3 variations of one font family. You have some addons (flickity.js/.css and chatinline.aspx) that are trying to load in before the page completely renders totaling 6s in wait time. Obviously this only addresses the items in your control. Time to first byte is measuring at 2.6s over 3G from Australia which is most likely the cause for Google Insight’s rating.


#19

Try loading most of the data only when user scrolls down.


#20

@neerja – Wishing you and the Bubble a Happy New Year.

Is there an update or ETA on this issue with Mobile Speeds ?