Thanks for the suggestion! We’re glad you enjoyed the video. We’re planning to cover layout shifts, FCP, LCP, and render-blocking resources in upcoming videos. Stay tuned!
I dont understand, why ver=xyz is better than ver=1.0.0? I think, that "ver" value developer changing only after changing content of file, not randomly
ver=xyz (where xyz is just an example) is a hash of the file, meaning it's a unique identifier based on the file's content. If the file changes, the hash changes too, ensuring browsers always fetch the latest version. From what we've seen, most developers use version numbers like ver=1.0.0 instead of a hash. This can lead to caching issues since the version number might not change even when the file content does. Using a hash like ver=xyz ensures that only actual content changes trigger a new version, improving performance and cache accuracy.
Great explanation! 👏
Thanks! 😃
Nice video. Can you do one on layout shifts, FCP, LCP and render blocking resources? I know I'm asking a lot.
Thanks for the suggestion! We’re glad you enjoyed the video. We’re planning to cover layout shifts, FCP, LCP, and render-blocking resources in upcoming videos. Stay tuned!
I dont understand, why ver=xyz is better than ver=1.0.0? I think, that "ver" value developer changing only after changing content of file, not randomly
ver=xyz (where xyz is just an example) is a hash of the file, meaning it's a unique identifier based on the file's content. If the file changes, the hash changes too, ensuring browsers always fetch the latest version.
From what we've seen, most developers use version numbers like ver=1.0.0 instead of a hash. This can lead to caching issues since the version number might not change even when the file content does. Using a hash like ver=xyz ensures that only actual content changes trigger a new version, improving performance and cache accuracy.