7 Messages
•
122 Points
Poor Website Performance
I've been a user of IMDB for several years, and have in all that time never had any reason to complain. Until now.
Basic site navigation is through links used to give nearly instant results with the old version of the site, even when using a 4Mb/s ADSL line (I do not have access to fibre or other faster connection tech).
Ever since the site was "redesigned" and "improved", it has become slow and sluggish. Almost impossible to use. The only time performance ever improves is when a link is directed to a part of the site that still uses the old IMDB design views.
- If I go to The Crown, the page takes in excess of 35 seconds to load.
- Scrolling to "Browse Episodes" and then clicking on the link to open the Season dropdown and clicking "4", opens the details for Season 4 loads the pages in 15 seconds.
- Further, if I click on the title of an episode, the details page for that episode takes 16 seconds to load....
- ....then if I click "Back" on my browser to return to the full episodes list for the season, it loads in 12 seconds (saving only 3 seconds) almost as if it is not using browser caching at all.
To illustrate, here are comparative page load times for "The Crown" on IMDB and TheMovieDB, after clearing the browser cache:
| IMDB | The Movie Database | |
| "The Crown" main page | 35 Seconds | 3 seconds |
| Season 4 Episodes List | 15 seconds | 2 seconds |
| Episode 4.1 Details Page | 16 seconds | <1 Second (opens in-page) |
| Browser "Back" to S4 Episodes List | 12 Seconds | <1 Second |
I understand that timings of 35, 15 and 12 seconds may not seem like much at, but time is everything, and when compared to performance timings of other sites, are far too high.
I have found that this lethargic performance of IMDB.COM is repeated across multiple browsers:
- Chromium Edge 92.0.902.73
- Google Chrome 92.0.4515.159
- Firefox 89.0.2
The IMDB App on Android is even slower and has a tendency to crash and bring overall tablet performance to a crawl.
Please investigate and try to fix this issue.
Thanks.
No Responses!