-
Notifications
You must be signed in to change notification settings - Fork 660
Site Load is too slow #1071
Comments
I can totally agree with @skamansam because I tried exactly the same and result is very poor here is result of my lighthouse audit. in my case I did not do the build process, I just used polymer serve and then audited the app in chrome with lighthouse. |
@touseefbsb I ran the bundled version because it generates the service worker and caching info, which improves the scores all around. |
@skamansam To clarify, are you running this against a real server with HTTP 2 support? Or against |
Polymer Starter Kit v3.2.0 hosted in Firebase. Preset: The performance section is not very good. 😕
Updated at #1071 (comment) |
@abdonrd something looks wrong there... From the results, that looks like an unbundled build. There's definitely a penalty for unbundled in 2.0 because the library is so much more granular. Can you check your build and see if it's getting bundled properly? Could be a CLI issue... |
Oops! I don't understand what happened. Updated Polymer Starter Kit v3.2.0 hosted in Firebase. Preset:
|
We can improve the best practices with Reference: https://github.com/Polymer/polymer/releases/tag/v2.1.0 |
@abdonrd that seems like a good change to me |
@robdodson & @keanulee: we only need to add this, right? Polymer.setPassiveTouchGestures(true); And the right place should be in the Or in the |
It would need to be after |
Now, with the last PR merged, we have better results: #1075 (comment). 👏 @robdodson @keanulee and I guess we could improve the performance section a bit more, what do you think? |
Description
When running the PSK with no code modifications against Lighthouse, it gives very low performance score across all builds due to the poor times for First Meaningful Paint, First Interactive, and Consistently Interactive.
Expected outcome
All load times are less than 3 seconds, and pass the Lighthouse performance rating with a 100.
Actual outcome
Steps to reproduce
polymer build
The text was updated successfully, but these errors were encountered: