Is startify causing my slow launch?

Nobody has claimed this yet.

Hi. Recently, once in a while, not every time by any means, gvim takes an absolute age to start. I am profiling the timings, and a typical startup might look like:

```

468.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline-themes\autoload\airline\themes\deus.vim
497.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\builder.vim
499.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\extensions\default.vim
523.000 169.000: opening buffers
524.000 001.000: BufEnter autocommands
524.000 000.000: editing files in windows
531.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\autoload\startify.vim
533.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\extensions\tabline\buflist.vim
536.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\autoload\startify\fortune.vim
912.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\syntax\startify.vim
916.000 391.000: VimEnter autocommands
916.000 000.000: before starting main loop
931.000 015.000: first screen update
931.000 000.000: --- VIM STARTED ---
```

But once in a while I get something like:

```

501.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline-themes\autoload\airline\themes\deus.vim
531.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\builder.vim
534.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\extensions\default.vim
558.000 183.000: opening buffers
558.000 000.000: BufEnter autocommands
558.000 000.000: editing files in windows
565.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\autoload\startify.vim
567.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-airline\autoload\airline\extensions\tabline\buflist.vim
571.000 001.000 001.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\autoload\startify\fortune.vim
43649.000 000.000 000.000: sourcing c:\Users\\OneDrive\vimfiles\bundle\vim-startify\syntax\startify.vim
43653.000 43093.000: VimEnter autocommands
43653.000 000.000: before starting main loop
43669.000 016.000: first screen update
43669.000 000.000: --- VIM STARTED ---
```

Is the above pointing to an issue with the startify plugin? The only change I am aware of in recent weeks is that I am using a VPN more or less full time.

Start with the profiling entries for autoload/startify.vim, autoload/startify/fortune.vim, and syntax/startify.vim, then inspect the VimEnter timing during both normal and delayed launches. Compare runs with the VPN context described in the report. Done means establishing whether startify is responsible for the delay and documenting or addressing the confirmed cause.

Written by the indexing model from the issue text.