Connecting to my site takes extremely long time

Can somebody please help and tell how to shorten the time to upload my site’s pages (powered by weebly): (about 18.9 ms to load)

I have many images in the site and was wondering if there is a way how to compress the data.



If you are using weebly you are going to find it tough to take control of site speed.

Regarding images:

First of all choose the right image format for the right job. There three commonly used image format for websites:


GIF is the most website friendly, for it generates a much smaller image file than the other two formats. It is best used when the images do not have a lot of colors in it or is black and white.

JPEG is a very commonly used image format. Since it support a color pallet of over 16 million shades, JPEG is often used in photo prints. JPEG files are much larger than GIF.

PNG have excellent color and flexibility. The best part about PNG is that you can create images without a background color, so it can take on any background you have. PNG creates pretty large files, so it is best used for smaller images such as logos and icons.

Choosing the right image format for the right job will greatly increase your website efficiency. In places where you do not need high quality images, you can use formats with small file sizes to achieve the same effect.

Weebly will automatically compress images but there are a number of image compressors available online to help you control the size of your images.

Most importantly, properly sizing images can save many bytes of data. From the Developers at Google:

Sometimes you may want to display the same image in various sizes, so you will serve a single image resource and use HTML or CSS in the containing page to scale it.

For example, you may have a 10 x 10 thumbnail version of a larger 250 x 250 image, and rather than forcing the user to download two separate files, you use markup to resize the thumbnail version.

This makes sense if the actual image size matches at least one - the largest - of the instances in the page, in this case 250 x 250 pixels. However, if you serve an image that is larger than the dimensions used in all of the markup instances, you are sending unnecessary bytes over the wire.

You should use an image editor to scale images to match the largest size needed in your page, and make sure that you specify those dimensions in the page as well.


A fat page is a SLOW page, every time. How fast do you think a 10 MEGABYTE page should load on a browser?

First off, click on every link on this page that says “analyze JPEG” and WPT will give you the optimized version of your image. Third choice is usually the smallest. Download these to your computer, rename them to match what’s on the server, and upload to overwrite. You’re saving 7.5 megabytes just by doing this, without losing anything on the page. Here’s the specific list:[code]Compress Images: 23/100

9,808.8 KB total in images, target size = 2,305.5 KB - potential savings = 7,503.3 KB

FAILED - (673.4 KB, compressed = 139.9 KB - savings of 533.5 KB) -
FAILED - (545.1 KB, compressed = 81.4 KB - savings of 463.7 KB) -
FAILED - (527.8 KB, compressed = 107.4 KB - savings of 420.5 KB) -
FAILED - (523.9 KB, compressed = 104.4 KB - savings of 419.5 KB) -
FAILED - (534.3 KB, compressed = 125.8 KB - savings of 408.5 KB) -
FAILED - (520.7 KB, compressed = 119.1 KB - savings of 401.6 KB) -
FAILED - (503.5 KB, compressed = 106.2 KB - savings of 397.4 KB) -
FAILED - (535.1 KB, compressed = 140.0 KB - savings of 395.1 KB) -
FAILED - (471.6 KB, compressed = 91.4 KB - savings of 380.2 KB) -
FAILED - (460.0 KB, compressed = 111.4 KB - savings of 348.6 KB) -
FAILED - (443.9 KB, compressed = 101.9 KB - savings of 342.0 KB) -
FAILED - (440.2 KB, compressed = 100.2 KB - savings of 340.0 KB) -
FAILED - (439.1 KB, compressed = 99.6 KB - savings of 339.5 KB) -
FAILED - (408.2 KB, compressed = 87.9 KB - savings of 320.3 KB) -
FAILED - (403.6 KB, compressed = 86.3 KB - savings of 317.3 KB) -
FAILED - (417.5 KB, compressed = 101.8 KB - savings of 315.7 KB) -
FAILED - (385.8 KB, compressed = 74.5 KB - savings of 311.3 KB) -
FAILED - (393.7 KB, compressed = 82.6 KB - savings of 311.1 KB) -
FAILED - (355.9 KB, compressed = 70.5 KB - savings of 285.4 KB) -
FAILED - (291.3 KB, compressed = 55.0 KB - savings of 236.3 KB) -
FAILED - (108.3 KB, compressed = 54.8 KB - savings of 53.5 KB) -
FAILED - (60.5 KB, compressed = 26.8 KB - savings of 33.7 KB) -
FAILED - (60.4 KB, compressed = 27.2 KB - savings of 33.2 KB) -
FAILED - (59.2 KB, compressed = 26.4 KB - savings of 32.9 KB) -
FAILED - (53.1 KB, compressed = 23.1 KB - savings of 30.1 KB) -
FAILED - (51.5 KB, compressed = 23.2 KB - savings of 28.3 KB) -
FAILED - (2.6 KB, compressed = 1.3 KB - savings of 1.3 KB) -
FAILED - (2.0 KB, compressed = 1.0 KB - savings of 1.0 KB) -
FAILED - (1.9 KB, compressed = 1.0 KB - savings of 0.9 KB) -
FAILED - (1.9 KB, compressed = 1.1 KB - savings of 0.8 KB) -[/code]

Next you need to Leverage browser caching of static assets. This is simple if you’re on a linux server by using the .htaccess file. Insert this code at the top of the file:<IfModule mod_expires.c> ExpiresActive On ExpiresByType text/css A2628000 ExpiresByType text/richtext A3600 ExpiresByType image/svg+xml A3600 ExpiresByType text/plain A3600 ExpiresByType text/xsd A3600 ExpiresByType text/xsl A3600 ExpiresByType video/asf A2628000 ExpiresByType video/avi A2628000 ExpiresByType image/bmp A2628000 ExpiresByType application/java A2628000 ExpiresByType video/divx A2628000 ExpiresByType application/msword A2628000 ExpiresByType application/x-msdownload A2628000 ExpiresByType image/gif A2628000 ExpiresByType application/x-gzip A2628000 ExpiresByType image/x-icon A2628000 ExpiresByType image/jpeg A2628000 ExpiresByType application/ A2628000 ExpiresByType audio/midi A2628000 ExpiresByType video/quicktime A2628000 ExpiresByType audio/mpeg A2628000 ExpiresByType video/mp4 A2628000 ExpiresByType video/mpeg A2628000 ExpiresByType application/javascript A2628000 ExpiresByType application/x-javascript A2628000 ExpiresByType application/ A2628000 ExpiresByType application/vnd.oasis.opendocument.database A2628000 ExpiresByType application/vnd.oasis.opendocument.chart A2628000 ExpiresByType application/vnd.oasis.opendocument.formula A2628000 ExpiresByType application/ A2628000 ExpiresByType application/vnd.oasis.opendocument.presentation A2628000 ExpiresByType application/vnd.oasis.opendocument.spreadsheet A2628000 ExpiresByType application/vnd.oasis.opendocument.text A2628000 ExpiresByType audio/ogg A2628000 ExpiresByType application/pdf A2628000 ExpiresByType image/png A2628000 ExpiresByType application/ A2628000 ExpiresByType audio/x-realaudio A2628000 ExpiresByType application/x-shockwave-flash A2628000 ExpiresByType application/x-tar A2628000 ExpiresByType image/tiff A2628000 ExpiresByType audio/wav A2628000 ExpiresByType audio/wma A2628000 ExpiresByType application/ A2628000 ExpiresByType application/ A2628000 ExpiresByType application/zip A2628000 </IfModule>

Doing just these two things will speed your site up toweringly.

As Anton said…

  1. Fix your Apache config - turn on compression + expires tags.

  2. Compress + Progressify all your .jpeg images, which you can do for all images at once using something like ImageMagick on the command line.

Write a script that goes through + saves original image + compresses/progresifies all images on server.

I agree with what the other posters have said above in the thread - dealing with the images would be my number 1 priority straight of the gate on this one.

I would also consider ditching one of the fonts used on your website and consolidating the CSS files into as few as possible (possibly even 1 if you use @import to import your Google fonts CSS as well).

Looks like you’ve made good progress improving your site.

On simple thing you can do to improve your site a more is to compress/strip/progressify your jpeg images.

I use ImageMagick convert for this with a command line incantation similar to…

convert $in -strip -interlace Plane -quality 95% $out