Google Speed Test Report Suggestions

https://stevendcohen.net/

1. Problem: Reduce JavaScript Execution Time (2.0 s):

Solution: Optimize the JavaScript code by minimizing the complexity and size of scripts.
This happens by breaking down long tasks into smaller ones, using web workers for
parallel processing, and removing unnecessary code. Consider using code-splitting to
load only the essential parts of JavaScript on the initial load.

How We Can Make JavaScript Run Faster:

--- Smaller code: Remove “extra stuff” from JavaScript code.
--- Load less: Only load JavaScript when needed.
--- Organize code: Make JavaScript easier to understand on the backend.
--- Use tools: There are special tools/plugins that can help JavaScript run faster.

Javascript Files with Issues (Per The Google Speed Test):

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

Google Tag Manager Files In This Issue :

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://www.googletagmanager.com/gtag/js?id=UA-49926708-1

Google Analytics File In This Issue :

https://www.google-analytics.com/analytics.js
2. Problem: Minimize Main-Thread Work (5.8 s):

Problem Explanation: The browser's rendering process is what turns code into a web
page that users can interact with. By default, the main thread of the renderer process
typically handles most code (it parses the HTML and builds the DOM, parses the CSS and
applies the specified styles, and parses, evaluates, and executes the JavaScript). It also
processes user events. So, any time the main thread is busy doing something else, the
web page may not respond to user interactions, leading to a poorer experience.

Solution: Reduce the time spent parsing, compiling and executing JavaScript. Delivering
smaller JavaScript payloads helps with this.

How to Make The Website Load Faster and Feel Smoother:

--- Less JavaScript: Using less JavaScript or making it smaller.
--- Quick CSS: Load only the needed styles fast.
--- Smart loading: Load things only when needed.

Current Loads:

3. Problem: Largest Contentful Paint (4,360 ms):

Problem Explanation: This is the largest contentful element painted within the viewport.
 Solution: Improve the Largest Contentful Paint (LCP) by optimizing the image, using
efficient CSS and JavaScript, and ensuring that the server response time is quick. Preload
is important along with using responsive images.

To Make the Website Load Quickly and Look Good:

--- Use smaller pictures: Making the images smaller (without losing quality) will improve
load speed.
--- Less waiting: Update what loads when so that only important things are loaded first,
like the main content or spot on the page they go to.
--- Speedy code: Making the overall website's code faster.

4. Problem: Reduce Unused CSS (Potential Savings of 219 KiB):

Problem Explanation: This problem wants to reduce unused rules from stylesheets and
defer CSS not used for above-the-fold content to decrease bytes consumed by network
activity.

Solution: Remove unused CSS. Make sure only the necessary CSS is included in the
production build.

To Make the Website Load Quickly:

--- Remove unused styles: Get rid of styles that aren’t needed (this can include anything
in the background or unnecessary plugins).
--- Load important styles first: Make sure the most important styles load first and quickly
and then the others.
 CSS file with Issues as Per The Google Speed Test:
https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

5. Problem: Eliminate Render-Blocking Resources (Potential Savings of 910 ms):

Problem Explanation: Resources are blocking the first paint of the page. Consider
delivering critical JavaScript/CSS inline and deferring all non-critical JavaScript styles.

Solution: Load critical CSS inline and defer non-essential CSS and JavaScript. Use the
async or defer attributes for external JavaScript files. (Technical/developer adjustments
on the backend).

To Make the Website Load Quickly:

--- Load important things first: Make sure the most important parts of your website load
first and fast by adjusting the load speed and timing of the webpage(s).
--- Combine files: Put small files together to load faster.

CSS & JS Files with Issues as Per The Google Speed Test:

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js


6. Problem: Serve Static Assets with an Efficient Cache Policy (1 Resource Found):

Problem Explanation: A long cache lifetime can speed up repeat visits to the page.

Solution: Implement proper cache headers for static assets to ensure they are cached
effectively by browsers. Set cache policies like max-age or Cache-Control headers.

How To Fix "Serve Static Assets with an Efficient Cache Policy":

--- Set cache headers: Configure your server to add cache headers for static assets (like
images, CSS, and JavaScript) using Cache-Control and Expires.
--- Use a long cache duration: Set a long cache duration (e.g., max-age=31536000) for
assets that don't change often.
--- Use a CDN: Serve assets from a Content Delivery Network (CDN) to improve load
times and cache effectiveness.

File with Issues as Per The Google Speed Test:

https://www.google-analytics.com/analytics.js

7. Problem: Does Not Use Passive Listeners to Improve Scrolling Performance:

 Problem Explanation: Consider marking touch and wheel event listeners passively to
improve the page's scroll performance.

Solution: Add { passive: true } to event listeners where appropriate, especially for scroll
and touch events, to improve performance and responsiveness.

How To Fix Scrolling Performance:

--- Update event listeners: When adding event listeners for scroll or touch events, use {
passive: true } to tell the browser these events won’t call preventDefault(), allowing
smoother scrolling.
--- Check all event listeners: Update all scroll and touch event listeners in your codebase
to use passive listeners.
^ This improves scrolling performance by letting the browser optimize the handling of
these events.

File with Issues as Per The Google Speed Test:

https://stevendcohen.net:1463:0

8. Problem: Defer offscreen Images:

Problem Explanation: Consider lazy-loading offscreen and hidden images after all critical
resources have finished loading to lower the time to interactive.

Solution: Use lazy loading for offscreen images. Implement the loading="lazy" attribute
or defer the image loading plugin until they are needed.

To fix "Defer Offscreen Images":

--- Use lazy loading: Add the loading="lazy" attribute to your <img> tags. This defers
loading images until they are close to being visible on the screen.
--- Implement intersection observer: For more control, use JavaScript’s Intersection
Observer API to load images only when they are near the viewport.
^These steps help reduce initial load time by deferring the loading of images that aren’t
immediately visible.

Image URLs with issue as per the Google speed test:

https://stevendcohen.net/wp-content/uploads/2020/08/Public-Speaking-Trainer-Steven
-Cohen.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/public-speaking-training-04.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-trainer-02.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/Steven-Cohen-public-speaking-
coach-1.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-coach-05.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-trainer-06.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-coach-01.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-coach-07.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/Steven-Cohen-Public-Speaking-
Trainer-2.jpg

https://www.stevendcohen.net/wp-content/uploads/2020/09/Dr-Steven-Cohen-Public-
Speaking-Coaching.jpg?id=1251

https://stevendcohen.net/wp-content/uploads/2020/09/Dr-Steven-Cohen-Public-Speaki
ng-Coaching.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-coach-03.jpg

https://stevendcohen.net/wp-content/uploads/2020/10/mobile-Dr-Steven-Cohen-Publi
c-Speaking-Coaching.jpg

https://stevendcohen.net/wp-content/uploads/2020/10/mobile-Steven-Cohen-Public-S
peaking-Trainer-1.jpg
 https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-trainer-08.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/public-speaking-video-2.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-video-1.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-trainer.png

https://stevendcohen.net/wp-content/uploads/2020/08/Dr-Steven-Cohen-Public-Speaki
ng-Trainer-Clients-768x65.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/public-speaking-coach.png

9. Problem: Avoid Serving Legacy JavaScript to Modern Browsers (Potential Savings of 0

KiB)

Problem Explanation: Polyfills and transforms enable legacy browsers to use new
JavaScript features. However, many aren't necessary for modern browsers. For bundled
JavaScript, adopting a modern script deployment strategy using a module/nomodule
feature detection to reduce the amount of code shipped to modern browsers, while
retaining support for legacy browsers.

Solution: Ensure modern JavaScript features are used, and consider using tools to
transpile only for older browsers if needed. Use feature detection rather than browser
detection.

How To Fix: Avoid Serving Legacy JavaScript to Modern Browsers

--- Update the code: Rewrite JavaScript using the latest standards (ES6+), like let, const,
arrow functions, and async/await.
--- Transpile older code: Use tools to convert modern JavaScript into a format compatible
with older browsers if needed.
--- Remove legacy code: Avoid using outdated JavaScript features or libraries. Ensure
your codebase uses up-to-date practices and libraries.

Files with issues as per the Google speed test:

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
 optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

10. Problem: Reduce Unused JavaScript (Potential Savings of 223 KiB)

Problem Explanation: Reduce unused JavaScript and defer loading scripts until they are
required to decrease bytes consumed by network activity.

Solution: Similar to unused CSS, remove or split unused JavaScript. Use “tree-shaking" to
eliminate dead code and bundle only necessary scripts.

How To Fix: Reduce Unused JavaScript:

--- Analyze your code: Use tools like Chrome DevTools to identify and review unused
JavaScript.
--- Remove unnecessary code: Delete or comment out JavaScript code that is not
needed.
--- Use code splitting: Break your JavaScript into smaller chunks and load only what’s
needed for the current page.
--- Implement tree shaking: Use build tools like Webpack to remove unused code from
your bundles.

Files with issues as per the Google speed test:

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

Google Tag Manager:

https://www.googletagmanager.com/gtag/js?id=G-2F00WWMFL4&l=dataLayer&cx=c
https://www.googletagmanager.com/gtag/js?id=UA-49926708-1
11. Problem: Avoid Long Main-Thread Tasks (16 Long Tasks Found)

Problem Explanation: List the longest tasks on the main thread, which is useful for
identifying the worst contributors to input delay.

Solution: Break up long tasks into smaller chunks. Use requestIdleCallback or defer
non-essential JavaScript execution to avoid blocking the main thread.

How To Fix: Avoid Long Main-Thread Tasks:

--- Break up tasks: Divide large JavaScript tasks into smaller chunks using setTimeout,
requestIdleCallback, or similar techniques.
--- Optimize code: Review and optimize your code to make it more efficient and reduce
execution time.
--- Use web workers: Offload heavy computations to web workers to run them in the
background without blocking the main thread.

Files with issues as per the Google speed test:

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css
 https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

Google Tag Manager Files In This Issue:

https://www.googletagmanager.com/gtag/js?id=G-2F00WWMFL4&l=dataLayer&cx=c
https://www.googletagmanager.com/gtag/js?id=UA-49926708-1

12. Problem: Avoid Excessive DOM Size (750 Elements)

Problem Explanation: A large DOM will increase memory usage, cause longer style
calculations, and produce costly layout reflows.

Solution: Simplify the DOM structure by reducing the number of elements and
optimizing the HTML. Avoid deeply nested elements and unnecessary wrappers.

How To Fix: Avoid Excessive DOM Size:

--- Simplify HTML structure: Reduce the number of elements on your page by removing
unnecessary or redundant tags.
--- Optimize components: Use efficient and minimal HTML structures in your
components or templates.

13. Problem: Initial Server Response Time (570 ms)

Problem Explanation: Keep the server response time for the main document short
 because all other requests depend on it.

Solution: This time is acceptable but you can always consider optimizing server
performance. Using a content delivery network (CDN) and optimizing server
configurations will allow the website to maintain fast response times.

How To Fix: Initial Server Response Time:

--- Optimize server performance: Upgrade your server or hosting plan if needed.
--- Use caching: Implement server-side caching (like Varnish or Redis) to store and
quickly serve frequently requested content.
--- Enable compression: Use gzip or Brotli to compress server responses and reduce data
transfer time.
--- Minimize backend processing: Optimize your backend code and database queries to
reduce processing time.

Url with issues as per the Google speed test:

https://stevendcohen.net/

14. Problem: Minimize Third-Party Usage (Third-Party Code Blocked the Main Thread for
140 ms)

Problem Explanation: Third-party code can significantly impact load performance. Limit
the number of redundant third-party providers and try to load third-party code after the
page has primarily finished loading.

Solution: Limit the use of third-party scripts and ensure they are optimized. Consider
independently loading for third-party scripts and evaluating their impact on
performance.

How To Fix:
--- Load independently: Ensure third-party scripts are loaded independently so they
don’t block your page rendering.

Google Tag Manager Files In This Issue:

https://www.googletagmanager.com/gtag/js?id=G-2F00WWMFL4&l=dataLayer&cx=c

https://www.googletagmanager.com/gtag/js?id=UA-49926708-1

Google Analytics File In This Issue:

https://www.google-analytics.com/analytics.js

https://www.google-analytics.com/j/collect?v=1&_v=j101&a=39359211&t=pageview&_
s=1&dl=https%3A%2F%2Ffanyv88.com%3A443%2Fhttps%2Fstevendcohen.net%2F&ul=en-us&de=UTF-8&dt=Dr.%20Steven
%20Cohen%20%7C%20Presentation%20Training%20%26%20Speech%20Coaching&sd=2
4-bit&sr=412x823&vp=412x823&je=0&_u=YEBAAUABAAAAACAAI~&jid=1480987511&gj
id=1942701651&cid=374760707.1722972046&tid=UA-49926708-1&_gid=1633977563.1
722972046&_r=1&gtm=457e4850h2za200&gcd=13l3l3l3l1&dma=0&tag_exp=95250753
&jsscut=1&z=1064863263

https://analytics.google.com/g/collect?v=2&tid=G-2F00WWMFL4&gtm=45je47v0v8744
80089za200&_p=1722972046171&_gaz=1&gcd=13l3l3l3l1&npa=0&dma=0&tag_exp=95
250753&cid=374760707.1722972046&ul=en-us&sr=412x823&uaa=&uab=64&uafvl=Not
%252FA)Brand%3B8.0.0.0%7CChromium%3B126.0.6478.182%7CHeadlessChrome%3B12
6.0.6478.182&uamb=1&uam=moto%20g%20power%20(2022)&uap=Android&uapv=11.
0&uaw=0&are=1&frm=0&pscdl=noapi&_eu=AAAI&_s=1&sid=1722972047&sct=1&seg=
0&dl=https%3A%2F%2Ffanyv88.com%3A443%2Fhttps%2Fstevendcohen.net%2F&dt=Dr.%20Steven%20Cohen%20%7C%20
Presentation%20Training%20%26%20Speech%20Coaching&en=page_view&_fv=1&_ss=
1&tfd=2272

Google Fonts Files In This Issue:

https://fonts.gstatic.com/s/ebgaramond/v14/SlGUmQSNjdsmc35JDF1K5GR1SDk_YAPI.w
off2

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-NfNkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
 Gi-DPNkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-6_RkBI96.ttf

Google/Doubleclick Ads Files In This Issue:

https://stats.g.doubleclick.net/g/collect?v=2&tid=G-2F00WWMFL4&cid=374760707.172
2972046&gtm=45je47v0v874480089za200&aip=1&dma=0&gcd=13l3l3l3l1&npa=0&frm
=0&tag_exp=95250753

15. Problem: Avoid Large Layout Shifts (4 Layout Shifts Found)

Problem Explanation: These are the largest layout shifts observed on the page. Each
table item represents a single layout shift and shows the element that shifted the most.
Below each item are possible root causes that led to the layout shift. Some of these
layout shifts may not be included in the CLS metric value due to windowing.

Solution: Ensure that elements have reserved space and avoid layout changes that shift
content unexpectedly. Using fixed sizes for images and avoiding changing the dimensions
of content dynamically will also help.

How To Fix:
--- Reserve space: Use fixed sizes for images, ads, and other elements to prevent layout
shifts.
--- Avoid dynamic changes: Avoid making changes to the dimensions of elements after
they have loaded.
--- Use CSS for layout: Use CSS properties like min-height and min-width to ensure
elements don’t shift unexpectedly.

Url with Issues as Per The Google Speed Test:

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-6_RkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-NfNkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-DPNkBI96.ttf

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js
16. Problem: Avoid Non-Composited Animations (18 Animated Elements Found)

Problem Explanation: Animations which are not composited can be off-putting and
increase CLS.

Solution: To avoid non-composited animations and improve website speed:

How To Fix:
-- Use simple animations like fading, sliding, or rotating.
-- Keep animations smooth and avoid sudden jumps.
-- Load images and content efficiently.

17. Problem: Avoid Enormous Network Payloads (Total Size Was 1,681 KiB)

Problem Explanation: Large network payloads cost users real money and are highly
correlated with long load times.

Solution: To make the website load faster by making files smaller. Also consider showing
excerpts in post lists (e.g. via the more tag), reducing the number of posts shown on a
given page, breaking long posts into multiple pages, or using a plugin to lazy-load
comments.
How To Fix:
—Compress images: Make pictures smaller.
—Shrink code: Remove extra spaces and lines from the website's code.
—Combine files: Put multiple small files into one bigger one.

Url with issues as per the Google speed test:

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-js-1b43e767e8ef5aaeadff655b1b208a8e.js

https://stevendcohen.net/wp-content/uploads/2020/08/Public-Speaking-Trainer-Steven
-Cohen.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/public-speaking-training-04.jpg

https://stevendcohen.net/wp-content/uploads/2020/10/mobile-Public-Speaking-Trainer
-Steven-Cohen.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-trainer-02.jpg

https://stevendcohen.net/wp-content/uploads/2020/09/Steven-Cohen-public-speaking-
coach-1.jpg

https://stevendcohen.net/wp-content/uploads/2020/08/public-speaking-coach-05.jpg

Google Tag Manager Files:

https://www.googletagmanager.com/gtag/js?id=G-2F00WWMFL4&l=dataLayer&cx=c

https://www.googletagmanager.com/gtag/js?id=UA-49926708-1
18. Problem: Avoid Chaining Critical Requests (5 Chains Found)

Problem Explanation: The Critical Request Chains show you what resources are loaded
with a high priority.

Solution: To avoid chaining critical requests and make website load faster, consider
reducing the length of chains, reducing the download size of resources, or deferring the
download of unnecessary resources to improve page load.

How To Fix:
--- Inline critical CSS: Place essential CSS directly in the HTML <head>.
--- Use preload and prefetch: Add <link rel="preload"> and <link rel="prefetch"> for
important resources.
--- Defer non-essential JavaScript: Use defer or async attributes for JavaScript files.
--- Bundle and minify files: Combine and minify CSS and JavaScript to reduce the number
of requests.
--- Leverage browser caching: Set proper cache headers to reduce repeat requests
Url with issues as per the Google speed test:
https://stevendcohen.net/wp-content/uploads/siteground-optimizer-assets/siteground-
optimizer-combined-css-ac72ac4743cb7e0c1b5e3563c8a1f1ee.css

https://stevendcohen.net/wp-content/themes/dt-the7/fonts/icomoon-the7-font/icomo
on-the7-font.ttf?wi57p5

https://stevendcohen.net/wp-includes/js/jquery/jquery.min.js

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-6_RkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-NfNkBI96.ttf

https://fonts.gstatic.com/s/ebgaramond/v27/SlGDmQSNjdsmc35JDF1K5E55YMjF_7DPu
Gi-DPNkBI96.ttf