+ Reply to Thread
Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: Google PageSpeed Insights - Failing Grade for Flynax

  1. #1

    Post Google PageSpeed Insights - Failing Grade for Flynax

    I ran a PageSpeed Insights test by Google on my Flynax website found here:

    - https://developers.google.com/speed/pagespeed/insights/

    I do not understand much of the report, but I do understand Google gave my Flynax website a failing grade.

    The grade was 40 out of 100.

    Also, I am using SiteGround a pretty expensive top-rated hosting company build for speed.

    If you get a chance, can you run your website and provide the score.

    I am wondering if there is anything, I can do to solve the many issues indicated by Google

  2. #2
    Flynax developer Rudi's Avatar
    Join Date
    Dec 2014
    Location
    Planet Earth
    Posts
    2,261

  3. #3
    Rudi,

    The page link you provided does not have a solution.

    It just asks a question.
    Last edited by Joe Can; June 4, 2021 at 08:57 AM.

  4. #4
    Guru
    Join Date
    Jan 2013
    Location
    Australia
    Posts
    2,028
    I also have very poor mobile page speed outcomes. I am just too busy to look at it now but will shortly




    page speed.png
    Last edited by Pete Young; June 5, 2021 at 01:15 AM.
    Getting Started or Starting Over with Your Classified Site? then Get Ready Set Fly V 4.7.1 > quietSecrets.net

  5. #5
    Master
    Join Date
    Jul 2019
    Location
    Australia
    Posts
    497
    My mobile speed shows in green "average".
    We all running the same script, must have alot to do with your server speed.

  6. #6
    Guru
    Join Date
    Jan 2013
    Location
    Australia
    Posts
    2,028
    12 tasks to complete
    1
    Optimizing your site
    2
    Avoid landing page redirects
    3
    Avoid plug-ins
    4
    Configure the viewport
    5
    Enable compression
    6
    Improve server response time
    7
    Inline CSS
    8
    Leverage browser caching
    9
    Minify resources
    10
    Optimize Images
    11
    Optimize CSS delivery
    12
    Prioritize visual content
    13
    Remove render-blocking JavaScript
    14
    Size content to viewport
    15
    Size tap targets appropriately
    16
    Use asynchronous scripts
    17
    Use legible font sizes
    18
    Check your site yourself to find problems fast

    must have alot to do with your server speed.
    I pay for a premium service ? so they tell me.

    A list above with the tasks they want me to complete

    the first one has this sub set

    The following tips will allow you to optimize your site, continue through the rest of the tasks for more information on each and steps to complete them.

    Defer offscreen images: Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. [Learn more](https://web.dev/offscreen-images/).
    Reduce initial server response time: Keep the server response time for the main document short because all other requests depend on it. [Learn more](https://web.dev/time-to-first-byte/).
    Remove unused JavaScript: Remove unused JavaScript to reduce bytes consumed by network activity. [Learn more](https://web.dev/unused-javascript/).
    Eliminate render-blocking resources: Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. [Learn more](https://web.dev/render-blocking-resources/).
    Minify JavaScript: Minifying JavaScript files can reduce payload sizes and script parse time. [Learn more](https://web.dev/unminified-javascript/).
    Remove unused CSS: Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. [Learn more](https://web.dev/unused-css-rules/).
    Minify CSS: Minifying CSS files can reduce network payload sizes. [Learn more](https://web.dev/unminified-css/).
    Avoid serving legacy JavaScript to modern browsers: Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. [Learn More](https://philipwalton.com/articles/de...duction-today/)
    Serve images in next-gen formats: Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. [Learn more](https://web.dev/uses-webp-images/).
    Preload key requests: Consider using `` to prioritize fetching resources that are currently requested later in page load. [Learn more](https://web.dev/uses-rel-preload/).
    Getting Started or Starting Over with Your Classified Site? then Get Ready Set Fly V 4.7.1 > quietSecrets.net

  7. #7
    Guru
    Join Date
    Jan 2013
    Location
    Australia
    Posts
    2,028
    lol don't even understand half of that jargon? hope there is some easy stuff.
    Getting Started or Starting Over with Your Classified Site? then Get Ready Set Fly V 4.7.1 > quietSecrets.net

  8. #8
    Master
    Join Date
    Jul 2019
    Location
    Australia
    Posts
    497
    If you pay for premium service does not mean your site does not get throttled.
    If your on the wrong server you will never have the speed.
    Theres alot they wont tell you.
    How your CPU, memory gets throttled.
    I found that out the hard way and left for something better.

  9. #9
    My review of the report shows that a lot of the issues have to do with coding:

    - Preload key requests
    - Multiple page redirects
    - Unused JavaScript
    -Images in next-gen format
    - Reduce unused CSS
    - Minify JavaScript
    - Efficiently encode images
    - Text not visible during Webfont load
    - Code blocked for 510 ms
    - Image elements do not have explicit
    - Minimize main-thread work
    - Avoid an excessive DOM size
    - Reduce JavaScript execution time

    I hope that the new version of Flynax at least looks to see if any of the items on the list are easy fixes.

    I am using SiteGround which rates very high for preformance.

  10. #10
    Master
    Join Date
    Oct 2019
    Location
    Hungary
    Posts
    300
    With a little optimization, you get a pretty good score according to PageSpeed Insights. I managed to get the Mobile to get 82 points and the desktop display to get 98 points. Of course, there is a lot to improve in the script anyway.

+ Reply to Thread