ancillary sites consistently slow doc page loading
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Undecided
|
Unassigned | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
lately, i frequently see loading times in excess of 10sec on doc pages, often even refreshing an unchanged page. during these slowdowns, i can see that the page is hung up waiting to communicate with six or seven ancillary sites, such as:
google-analytics
crazyegg
usabilla
<something>-manager
possibly facebook-
i couldn't capture them all when trying to capture them for this bug, but i feel like i've seen additional sites.
if we can see and experience this, so can our customers. not sure how customers would feel about waiting for a doc page to load whilst all these tracking and monitoring sites are dragging down the browser. this may be necessary, but as it's structured now, it certainly isn't conducive to customer satisfaction or comfort. can we speed it up, and, if the ancillary sites really are valuable (some are), maybe hide them from the URL display when they're loading?
Changed in maas-ui: | |
importance: | Undecided → Unknown |
Changed in maas-ui: | |
status: | New → Fix Released |
Changed in maas: | |
milestone: | none → 2.9.0rc1 |
Changed in maas: | |
status: | Fix Committed → Invalid |
Bill,
I am 99% sure those aren't blocking rendering. I think it might be some jquery that seems to load slowly. But the problem seems to be the initial connection for the main html page.
Looking at the headers, I think this might be it
warning: 199 canonicalwebtea m.discourse- docs "Could not parse URL map item {item}" m.discourse- docs "Could not parse URL map item {item}" m.discourse- docs "Redirect path /docs/release-notes clashes with URL map"
warning: 199 canonicalwebtea
warning: 199 canonicalwebtea
Kit, Ant can you help?
Peter