Your Website Score is

Similar Ranking

14
MY BLOG – MY WORDPRESS BLOG
llwd.site
14
CONCEPT SAFETY SIGNS – COMPLIANCY AND SAFETY SIGNAGE SOUTH AFRICA
conceptsafetysigns.com
14
BOOKINGS DEMO |
bookings.limelite.in.net
14
IIS WINDOWS SERVER
tadex.co.za
12
سرویس اشتراک ویديو - تماشا
tamasha.com
12
MR VINÇ FORKLIFT MANLIFT KIRALAMA - ANKARA
mrvincforklift.com
12
FERHAT VINÇ FORKLIFT KIRALAMA - ANKARA
ferhatvinc.com.tr

Latest Sites

14
IIS WINDOWS SERVER
tadex.co.za
53
MARKET 50 DISCOUNT SALE
50discount-sale.com
99
YOUTUBE
youtube.com
31
FREEFORM® TENTS | STRETCH TENTS FOR SALE
freeformtents.com
19
FILON PROJECTS (PTY) LTD | SOUTH AFRICA, LESOTHO & MOZAMBIQUE
filonprojects.com
31
PROFESSIONAL ELECTRICAL SERVICE PROVIDER | ELECTRICAL ENGINEER | VOLTRIDGE
voltridge.co.za
19
SEO TOOLS BY LIMELITE | FREE ONLINE SEO TOOLS
seotools.limelitehosting.co.za

14 llwd.site Last Updated: 4 weeks

Success 63% of passed verification steps
Warnings 7% of total warnings
Errors 30% of total errors, require urgent action

Desktop

Mobile

Performance Desktop Score 58%
Best Practices Desktop Score 100%
SEO Desktop Score 83%
PWA Desktop Score 29%
Performance Mobile Score 53%
Best Practices Mobile Score 100%
SEO Mobile Score 86%
PWA Mobile Score 25%
Page Authority Authority 5%
Domain Authority Domain Authority 1%
Moz Rank 0.5/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 27 Characters
MY BLOG – MY WORDPRESS BLOG
Meta Description 0 Characters
NO DATA
Effective URL 17 Characters
https://llwd.site
Excerpt Page content
My Blog – My WordPress Blog Skip to content Home Services About ...
Keywords Cloud Density
elit13 dolor9 ipsum7 lorem7 amet7 consectetur7 mattis6 ullamcorper6 tellus6 luctus5
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
elit 13
dolor 9
ipsum 7
lorem 7
amet 7
consectetur 7
mattis 6
ullamcorper 6
tellus 6
luctus 5
Google Preview Google search result preview
MY BLOG – MY WORDPRESS BLOG
https://llwd.site
My Blog – My WordPress Blog Skip to content Home Services About ...
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~166.71 KB
Code Size: ~64.36 KB
Text Size: ~102.35 KB Ratio: 61.39%

Social Data

Only Registered Users

Sign up for see all features and reviews about this site

Login

Estimated Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Desktop

Desktop Screenshot
Avoids enormous network payloads Total size was 1,582 KiB
Large network payloads cost users real money and are highly correlated with long load times
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 1 element found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Avoid an excessive DOM size 580 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Avoid large layout shifts 1 layout shift found
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](https://web.dev/articles/cls#what_is_cls)
Avoid chaining critical requests 26 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Largest Contentful Paint element 4,690 ms
This is the largest contentful element painted within the viewport
Speed Index 6.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve static assets with an efficient cache policy 1 resource found
A long cache lifetime can speed up repeat visits to your page
Server Backend Latencies 150 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Initial server response time was short Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it
Minimizes main-thread work 0.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Largest Contentful Paint 4.7 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce unused CSS Potential savings of 24 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Efficiently encode images Potential savings of 79 KiB
Optimized images load faster and consume less cellular data
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Time to Interactive 6.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 3.9 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks 1 long task found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Defer offscreen images Potential savings of 25 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Network Round Trip Times 140 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
First Meaningful Paint 3.9 s
First Meaningful Paint measures when the primary content of a page is visible
Serve images in next-gen formats Potential savings of 773 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Eliminate render-blocking resources Potential savings of 4,570 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

Mobile

Mobile Screenshot
Eliminate render-blocking resources Potential savings of 5,950 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Network Round Trip Times 140 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance
Reduce unused CSS Potential savings of 24 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
JavaScript execution time 0.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Avoid an excessive DOM size 580 elements
A large DOM will increase memory usage, cause longer [style calculations](https://developers.google.com/web/fundamentals/performance/rendering/reduce-the-scope-and-complexity-of-style-calculations), and produce costly [layout reflows](https://developers.google.com/speed/articles/reflow)
Efficiently encode images Potential savings of 79 KiB
Optimized images load faster and consume less cellular data
Minimize main-thread work 2.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid non-composited animations 1 animated element found
Animations which are not composited can be janky and increase CLS
Defer offscreen images Potential savings of 25 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Document uses legible font sizes 99.78% legible text
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px
Uses efficient cache policy on static assets 0 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 26 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load
Avoid long main-thread tasks 4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Time to Interactive 11.0 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid large layout shifts 2 layout shifts found
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](https://web.dev/articles/cls#what_is_cls)
Avoid large layout shifts 3 elements found
These DOM elements were most affected by layout shifts. Some layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Server Backend Latencies 150 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance
Serve images in next-gen formats Potential savings of 773 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
First Meaningful Paint 6.2 s
First Meaningful Paint measures when the primary content of a page is visible
Minimize third-party usage Third-party code blocked the main thread for 0 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading
Avoids enormous network payloads Total size was 1,581 KiB
Large network payloads cost users real money and are highly correlated with long load times
Initial server response time was short Root document took 150 ms
Keep the server response time for the main document short because all other requests depend on it
Total Blocking Time 200 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 15.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements
First Contentful Paint 6.2 s
First Contentful Paint marks the time at which the first text or image is painted
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Largest Contentful Paint element 8,230 ms
This is the largest contentful element painted within the viewport
Largest Contentful Paint 8.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

Alexa Rank

Only Registered Users

Sign up for see all features and reviews about this site

Login

Server Information

Only Registered Users

Sign up for see all features and reviews about this site

Login