Skip to content

Resolve Issues from PageSpeed Report #12

@hkailahi

Description

@hkailahi

https://pagespeed.web.dev/analysis/https-heneli-dev-y2wl-oxg7bsa90-hkailahi-vercel-app-blog-fearless-tinkering-is-functional/p7hpyv1w17?form_factor=desktop

https://pagespeed.web.dev/analysis/https-heneli-dev-y2wl-oxg7bsa90-hkailahi-vercel-app-blog-fearless-tinkering-is-functional/p7hpyv1w17?form_factor=mobile


Hydration failed because the initial UI does not match what was rendered on the server. - https://legacy.reactjs.org/docs/error-decoder.html/?invariant=418
https://stackoverflow.com/questions/71706064/react-18-hydration-failed-because-the-initial-ui-does-not-match-what-was-render
facebook/react#24519 (comment)

Likely doesn't like <p> tags in tables or some other HTML.


There was an error while hydrating. Because the error happened outside of a Suspense boundary, the entire root will switch to client rendering.
https://reactjs.org/docs/error-decoder.html?invariant=423


Text content does not match server-rendered HTML.

vercel/next.js#38263
https://stackoverflow.com/questions/74461835/next-js-throws-error-text-content-does-not-match-server-rendered-html


Refused to load the script 'https://vercel.live/_next-live/feedback/feedback.js' because it violates the following Content Security Policy directive: "script-src 'self' 'unsafe-eval' 'unsafe-inline' giscus.app". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions