Ask a Question ?
Design & Publish Websites Faster

What Affects Breezi’s Speed

In this article we’ll explain several situations that have to do with our web tool speed. We’ll also address possible fixes where applicable.

Topics Covered

We’ll go over the following topics:

  1. CDN for Static App Files
  2. Minimum Memory Required
  3. Internet Connection Speed
  4. Avoid Intermittent Connections
  5. Recommended Browsers
  6. Avoid Developer Tools / Firebug
  7. Refresh the Editor

1. CDN for Static App Files

We use the Amazon CloudFront to serve all static files.

This service consists in delivering content from different locations throughout the world. Every request made is redirected to the closest server, so content is served as fast as possible.

For example, if a user is located in Australia, the requests for static files being made will head to a server in his/her country, instead of going to a server in the US or somewhere else.

The closer the server, the faster the transfer of files.

This only speeds your experience up, wherever you are located.

Amazon CloudFront representation

Note that the actual locations of the servers may not be accurately represented on this image

Note

We only serve static APP files from CDN, not for the public sites.

2. Minimum Memory Required

You’ll need at least 2GB of RAM to run pour web tool smoothly.

If you have less than this, you may be experiencing lags in your browser or in your computer in general.

RAM memory representation

In general, the more memory you have, the faster your computer will run

3. Internet Connection Speed

We transfers a lot of data back and forth, thus a fast connection is required.

2 MBPS (megabits per second) is recommended.

4. Avoid Intermittent Connection

Data is saved constantly, so if your Internet connection is being interrupted continuously, your site might suffer errors.

This issue is a delicate one. Data might get corrupt or not properly saved.

This can happen frequently on a wireless network. If you’re on Wifi, the further away you are from the router or access point, the faultier your connection will be.

Try getting closer to it.

5. Recommended Browsers

Latest versions of standard compliant browsers are required to work with our editor. And it’s also a good advise to use them for browsing any site.

Both Firefox’s and Chrome’s latest versions are advisable, though we’d suggest Firefox if we have to pick just one. At the time of writing this post, the latest versions are: Firefox 18.0.2 and Chrome 24.0.1312.57 m..

Mozilla Firefox and Google Chrome: recommended browsers

Recommended browsers for editing a site in our program

You can download them from these links:

Notes

 

6. Avoid Developer Tools / Firebug

There are several tools designed for for debugging HTML, CSS, JavaScript, network traffic and others. Depending on the specific browser, they may be called Firebug (for Firefox), Developer Tools (for Chrome) or Web Inspector for (Safari), among others.

They are sometimes called generically the “F12 Developer Tools”, referencing the keyboard shortcut that’s usually associated to them.

Google Chrome's Developer Tools

Keep the Developer Tools closed/hidden for better performance

These tools are very handy for developers as they debug code, functionality and other advanced issues not required for our program as all the functionality is already coded and built in.

Besides this and most importantly for performance and speed purposes, it is recommended to avoid having these tools opened when editing a site in our editor, since it can slow your browser down.

7. Refresh the Editor

If for some reason you feel your experience is a bit slow, you can try refreshing the editor (ctrl/cmd+R).

Get Help

If you’ve followed all these recommendations and are still having a slow experience, please contact support stating your setup and issue.

Menu