I’ve been testing my site a bit, and I was wondering if it was possible to preload background hero images automatically with Optimole? Google Lighthouse is warning me that my hero image is not preloaded in my metrics.
]]>https://prnt.sc/JW3d_5Lb5HVs
Kindly suggest how to make these link crawlable & seo friendly.
]]>First of all thank you for your plug-in.
I’m using the “Gallery (Adv)” block to a create a carrousel of 26 images. It works great, I’m picking the pictures from my Media gallery and they show perfectly fine in the carrousel, but when I test my website through Google Lighthouse it lowers my score and gives me several warnings stating that some of the pictures in my gallery are unable to be located “Unable to locate resource”. Is there a solution to this?
Thank you!
]]>the Google Lighthouse Viewer said I should remove unused CSS.
In the source code you can see
#cf7cstmzr-form.cf7cstmzr-form-146411 .wpcf7-form,
#cf7cstmzr-form.cf7cstmzr-form-146412 .wpcf7-form,
#cf7cstmzr-form.cf7cstmzr-form-146413 .wpcf7-form,
and so on.
How can I avoid this or only load at the site(s) where I have the contact forms?
Best regards,
Luke
We had a minor issue with the plugin not saving on Product category pages. I reached out to support and within a few short moments received a reply from Gabriel and supplied the fix.
Couldn’t be more pleased with Asset Cleanup Pro!
]]>A good question to ask is if meta tags are still necessary. They used to be more helpful, providing important information to the Internet browser. As browsers became more sophisticated, they stopped needing a lot of hand holding in order to figure out if your site is in English or Chinese.
This is what the documentation from Web.dev says:
The <meta name=”description”> element provides a summary of a page’s content that search engines include in search results. A high-quality, unique meta description makes your page appear more relevant and can increase your search traffic.
How the Lighthouse meta description audit fails #
Lighthouse flags pages without a meta description:
The blog post also gives the best practices for using meta descriptions:
Meta description best practices #
Use a unique description for each page.
Make descriptions clear and concise. Avoid vague descriptions like “Home.”
Avoid keyword stuffing. It doesn’t help users, and search engines may mark the page as spam.
Descriptions don’t have to be complete sentences; they can contain structured data.
There is also similar documentation on title meta tags:
Having a <title> element on every page helps all your users:
Search engine users rely on the title to determine whether a page is relevant to their search.
The title also gives users of screen readers and other assistive technologies an overview of the page. The title is the first text that an assistive technology announces.
How the Lighthouse title audit fails #
Lighthouse flags pages without a <title> element in the page’s <head>
There are also best practices for title tags:
Tips for creating great titles #
Use a unique title for each page.
Make titles descriptive and concise. Avoid vague titles like “Home.”
Avoid keyword stuffing. It doesn’t help users, and search engines may mark the page as spam.
It’s OK to brand your titles, but do so concisely.
Even though schema is not mentioned in the blog post and Google does not include it in Lighthouse, it is still an important aspect of SEO. A user might take the blog post to be all structured data is unimportant on a website. Google writes this about schema structured data on a documentation page:
Google Search works hard to understand the content of a page. You can help us by providing explicit clues about the meaning of a page to Google by including structured data on the page. Structured data is a standardized format for providing information about a page and classifying the page content; for example, on a recipe page, what are the ingredients, the cooking time and temperature, the calories, and so on.
Google uses structured data that it finds on the web to understand the content of the page, as well as to gather information about the web and the world in general.
If WordPress is not going to provide basic SEO in its core such as meta descriptions, meta titles, and schema.org markup and wants users to rely on plugins, it needs to be honest about this. Being honest will help users make an educated decision if they want to use WordPress even though it lacks basic SEO in its core features.
The blog post gaslights WordPress users into disregarding basic SEO as unimportant when Google considers it important enough to notify users they are not using unique meta descriptions on their pages.
The documentation should be edited or deleted.
The Site Kit plugin is slowing down my website. I am not running any tags on any of my pages. I have the plugin configured for:
I have Google Tag Manager but it the settings it is showing it is not connected to my website.
When I use the LightHouse tool, I am getting the following errors:
Remove unused JavaScript 1.19 s
URL
Transfer Size
Potential Savings
…jquery/jquery.min.js?ver=3.5.1(lazyjack.blog)
43.4 KiB
31.5 KiB
/gtm/js?id=OPT-5NWPB8G&t=gtag_UA_185…_1&cid=495….161…(www.google-analytics.com)
45.5 KiB
30.3 KiB
/gtag/js?id=UA-185…-1(www.googletagmanager.com)
53.1 KiB
28.4 KiB
/v0/amp-analytics-0.1.js(cdn.ampproject.org)
20.9 KiB
20.9 KiB
…extensions/amp-analytics/0.1/events.js
2.6 KiB
2.9 KiB
…extensions/amp-analytics/0.1/visibility-manager.js
1.7 KiB
2 KiB
…extensions/amp-analytics/0.1/amp-analytics.js
1.5 KiB
1.8 KiB
…extensions/amp-analytics/0.1/config.js
1 KiB
1.2 KiB
…extensions/amp-analytics/0.1/variables.js
0.9 KiB
1 KiB
Reduce the impact of third-party code Third-party code blocked the main thread for 250 ms
Google Analytics
64 KiB
237 ms
/analytics.js(www.google-analytics.com)
19 KiB
216 ms
/gtm/js?id=OPT-5NWPB8G&t=gtag_UA_185…_1&cid=495….161…(www.google-analytics.com)
45 KiB
21 ms
Google Tag Manager
53 KiB
17 ms
/gtag/js?id=UA-185…-1(www.googletagmanager.com)
53 KiB
17 ms
AMP
21 KiB
0 ms
/v0/amp-analytics-0.1.js(cdn.ampproject.org)
21 KiB
0 ms
Other Google APIs/SDKs
0 KiB
0 ms
]]>Reduce JavaScript execution time 1.4 s
URL
Total CPU Time
Script Evaluation
Script Parse
/start-here/?noamp=available(lazyjack.blog)
1,241 ms
51 ms
24 ms
Unattributable
1,228 ms
24 ms
1 ms
…jquery/jquery.min.js?ver=3.5.1(lazyjack.blog)
559 ms
334 ms
128 ms
/analytics.js(www.google-analytics.com)
365 ms
329 ms
31 ms
/start-here/(lazyjack.blog)
282 ms
44 ms
6 ms
/gtm/js?id=OPT-5NWPB8G&t=gtag_UA_185…_1&cid=495….161…(www.google-analytics.com)
157 ms
111 ms
36 ms
data:text/javascript;base64,IWZ1bmN0a…/ZnVuY3Rpb…
157 ms
152 ms
5 ms
/gtag/js?id=UA-185…-1(www.googletagmanager.com)
142 ms
117 ms
13 ms
/pwa-register-sw.js?ver=1.7.28(lazyjack.blog)
120 ms
10 ms
6 ms
Reduce the impact of third-party code Third-party code blocked the main thread for 830 ms
My page speed score has gone from 96 to 54.
Third-Party
Transfer Size
Main-Thread Blocking Time
AMP
240 KiB
832 ms
/v0.js(cdn.ampproject.org)
76 KiB
768 ms
/v0/amp-form-0.1.js(cdn.ampproject.org)
28 KiB
37 ms
/v0/amp-lightbox-0.1.js(cdn.ampproject.org)
14 KiB
23 ms
/v0/amp-bind-0.1.js(cdn.ampproject.org)
30 KiB
4 ms
/v0/amp-analytics-0.1.js(cdn.ampproject.org)
58 KiB
0 ms
Other resources
33 KiB
0 ms
Google Tag Manager
0 KiB
0 ms
Google Analytics
0 KiB
0 ms
Here is my information from Site Health:
### wp-core ###
version: 5.6
site_language: en_US
user_language: en_US
timezone: America/Los_Angeles
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 1
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 1
dotorg_communication: true
### wp-paths-sizes ###
wordpress_path: /home/dhosting.com/deborah86/lazyjack.blog/public_html
wordpress_size: 43.22 MB (45322742 bytes)
uploads_path: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content/uploads
uploads_size: 0.00 B (0 bytes)
themes_path: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content/themes
themes_size: 1.59 MB (1666834 bytes)
plugins_path: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content/plugins
plugins_size: 34.92 MB (36612720 bytes)
database_size: 11.19 MB (11730944 bytes)
total_size: 90.92 MB (95333240 bytes)
### wp-dropins (2) ###
advanced-cache.php: true
object-cache.php: true
### wp-active-theme ###
name: Twenty Twenty (twentytwenty)
version: 1.6
author: the WordPress team
author_website: https://www.ads-software.com/
parent_theme: none
theme_features: core-block-patterns, automatic-feed-links, custom-background, post-thumbnails, custom-logo, title-tag, html5, align-wide, responsive-embeds, customize-selective-refresh-widgets, editor-color-palette, editor-font-sizes, editor-styles, amp, widgets, menus, editor-style
theme_path: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content/themes/twentytwenty
auto_update: Disabled
### wp-plugins-active (5) ###
AMP: version: 2.0.9, author: AMP Project Contributors, Auto-updates enabled
Bing Webmaster Url Submission: version: 1.0.7, author: Bing Webmaster, Auto-updates enabled
LiteSpeed Cache: version: 3.6.1, author: LiteSpeed Technologies, Auto-updates enabled
PublishPress Blocks: version: 2.5.0, author: PublishPress, Auto-updates disabled
Site Kit by Google: version: 1.23.0, author: Google, Auto-updates enabled
### wp-media ###
image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1656
imagemagick_version: ImageMagick 6.7.8-9 2016-06-17 Q16 https://www.imagemagick.org
file_uploads: File uploads is turned off
post_max_size: 8192M
upload_max_filesize: 2048M
max_effective_size: 2 GB
max_file_uploads: 20
imagick_limits:
imagick::RESOURCETYPE_AREA: 126 GB
imagick::RESOURCETYPE_DISK: -1
imagick::RESOURCETYPE_FILE: 15000
imagick::RESOURCETYPE_MAP: 126 GB
imagick::RESOURCETYPE_MEMORY: 63 GB
imagick::RESOURCETYPE_THREAD: not available
gd_version: bundled (2.1.0 compatible)
ghostscript_version: unknown
### wp-server ###
server_architecture: Linux 3.10.0-714.10.2.lve1.5.19.7.el7.x86_64 x86_64
httpd_software: LiteSpeed
php_version: 7.3.3-dh20 64bit
php_sapi: litespeed
max_input_variables: 6000
time_limit: 3000
memory_limit: 8192M
max_input_time: 3000
upload_max_filesize: 2048M
php_post_max_size: 8192M
curl_version: 7.64.0 OpenSSL/1.0.2k
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true
### wp-database ###
extension: mysqli
server_version: 10.1.35-MariaDB-cll-lve
client_version: mysqlnd 5.0.12-dev - 20150407 - $Id: 7cc7cc96e675f6d72e5cf0f267f48e167c2abb23 $
### wp-constants ###
WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content
WP_PLUGIN_DIR: /home/dhosting.com/deborah86/lazyjack.blog/public_html/wp-content/plugins
WP_MAX_MEMORY_LIMIT: 8192M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined
### wp-filesystem ###
wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
### google-site-kit ###
version: 1.23.0
php_version: 7.3.3-dh20
wp_version: 5.6
reference_url: https://lazyjack.blog
amp_mode: primary
site_status: connected-site
user_status: authenticated
connected_user_count: 1
active_modules: site-verification, search-console, analytics, pagespeed-insights, optimize, tagmanager
required_scopes:
openid: ✅
https://www.googleapis.com/auth/userinfo.profile: ✅
https://www.googleapis.com/auth/userinfo.email: ✅
https://www.googleapis.com/auth/siteverification: ✅
https://www.googleapis.com/auth/webmasters: ✅
https://www.googleapis.com/auth/analytics.readonly: ✅
https://www.googleapis.com/auth/tagmanager.readonly: ✅
capabilities:
googlesitekit_authenticate: ✅
googlesitekit_setup: ✅
googlesitekit_view_posts_insights: ✅
googlesitekit_view_dashboard: ✅
googlesitekit_view_module_details: ✅
googlesitekit_manage_options: ✅
googlesitekit_publish_posts: ✅
search_console_property: https://lazyjack.blog/
analytics_account_id: 1858?????
analytics_property_id: UA-1858???????
analytics_profile_id: 2348?????
analytics_use_snippet: yes
optimize_id: OPT-5NW????
tagmanager_account_id: 6002??????
tagmanager_container_id: none
tagmanager_amp_container_id: GTM-57Z????
tagmanager_use_snippet: yes
### amp_wp ###
amp_mode_enabled: standard
amp_reader_theme: legacy
amp_templates_enabled: post, page, attachment, is_singular, is_front_page, is_home, is_archive, is_author, is_date, is_search, is_404, is_category, is_tag
amp_serve_all_templates: true
amp_css_transient_caching_disabled: n/a
amp_css_transient_caching_threshold: 5000 transients per day
amp_css_transient_caching_sampling_range: 14 days
amp_css_transient_caching_transient_count: 31
amp_css_transient_caching_time_series:
20201231: 31
amp_libxml_version: 2.9.1
Reduce initial server response time
When I disable the plugin, the page speed score goes up. I have tested this on multiple websites. I think it has to do with the QUIC.cloud CDN.
Report Numbers
https://t.dcompany.site/ XJDFMTRE
https://lazyjack.blog/ YDUKVQZU
https://t.dhostingsites.com/ RMOYFOBI