Outlook 2013 Very Slow



  • I moved to Office 2013 about 4 months ago and I've noticed that it's considerably slower than Outlook 2010.

    Sometimes when I delete an item it will stay in the box until I either click on another email or I use the arrow keys to switch to a new item.

    I'm not using cached mode.

    I'm writing this after seeing a thread in another forum which has led me to ask if other people have noticed that Outlook 2013 is quirky compared to 2010?

    Maybe I'll install Office 2010 too and just compare my own experiences.

    The PC is a HP EliteDesk 800 G1 SFF with 12 Gig RAM and a SSD.



  • Why no cached mode? I would assume the delay you are seeing is communication lag with the server for some reason. No idea though as I always have outlook installed in coached mode.



  • Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.



  • As a company almost everyone in the company has full access to our physicians calendars that they need to edit and update regularly. I've seen several instances where while running in cached mode users won't see other people's edits to a third person's calendar for a noticeable amount of time. This is a work flow problem at least and a double booking problem at worse. Running in non cache mode completely solves this problem. I can't recall seeing the issues I'm now experiencing in Outlook 2013 when I was using Outlook 2010.



  • @scottalanmiller said:

    Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.

    I'm recall reading this somewhere in the past.

    I understand the move to web apps, but I have to say personally I just am not a fan!



  • It will get better and better. The transition point is always painful. JavaScript is the future. It gets more powerful every day.



  • This site is pure JavaScript, for example.



  • Office 2013's designed to be less system-intensive, and that comes at the expense of slower screen/folder updates, passive spell checking, shorter default cached data periods, etc. The goal was to make it feasible to run the full application on mobile devices while sipping at the battery gently.



  • @scottalanmiller said:

    Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.

    Really?

    @scottalanmiller said:

    Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.



  • Yes. LibreOffice did it first but it was optional only. To prepare for hosted Office they had to get it built in JavaScript first. Watch it really closely and you can tell. But they did a great job.



  • @scottalanmiller said:

    Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.

    Are you sure on that? I just took a stroll through my office directory and found all the appropriate DLL files and such that would go along with a regular program. Outlook still has all the native quirks, features, and errors that wouldn't be part of a web app.



  • @Nara said:

    @scottalanmiller said:

    Office 2013 is slower. It just is. You have moved from a Windows native app to a web app. They don't tell you this anywhere but look closely. Office 2013 is actually running in a frameless browser.

    Are you sure on that? I just took a stroll through my office directory and found all the appropriate DLL files and such that would go along with a regular program. Outlook still has all the native quirks, features, and errors that wouldn't be part of a web app.

    The interface is running in the browser. It still has some hooks because lots of stuff needs the DLLs. But the part that you see is all in a frameless browser. Lots of applications run this way, it is a lot of Microsoft's vision for the future and makes sense for portability and hostability.