Your Website Score is

Similar Ranking

24
APARTEL RESORTS - СХІДНИЦЯ
sales.apartel-resorts.com
24
ESTIMATE YOUR SITE WORTH | WORTH MY SITE
giveapp.org
24
SAVE-UKRAINE.TODAY
heroes.save-ukraine.today
23
WEBSITE DESIGN SUNSHINE COAST AND BRISBANE | SEO SERVICES
paulbarrs.com
23
SEO MANCHESTER | SEO AGENCY MANCHESTER: REQ
seoreq.com
23
WEB TO PRINT | WEB TO PRINT SOFTWARE | WEB2PRINT (W2P) SOLUTION
wtpbiz.com
23
ANTI VIBRATION TECHNOLOGIES
antivibrationtable.com

Top Technologies

Google Font API
Font Scripts
WordPress
CMS
CloudFlare
CDN
Font Awesome
Font Scripts
Apache
Web Servers
Nginx
Web Servers
Twitter Bootstrap
Web Frameworks
LiteSpeed
Web Servers

24 heroes.save-ukraine.today Last Updated: 1 year

Success 39% of passed verification steps
Warning 38% of total warning
Errors 23% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 98%
Best Practices Desktop Score 55%
SEO Desktop Score 90%
PWA Desktop Score 29%
Performance Mobile Score 88%
Best Practices Mobile Score 55%
SEO Mobile Score 92%
PWA Mobile Score 38%
Page Authority Authority 12%
Domain Authority Domain Authority 6%
Moz Rank 1.2/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 18 Characters
SAVE-UKRAINE.TODAY
Meta Description 48 Characters
Este posibil ca acest domeniu să fie de vânzare!
Effective URL 32 Characters
http://heroes.save-ukraine.today
Excerpt Page content
save-ukraine.today save-ukraine.today Cumpăraţi acest domeniu. 2023 Copyright. ...
Keywords Cloud Density
save1 ukraine1 today1 cumpăraţi1 acest1 domeniu1 copyright1 rights1 reserved1 privacy1
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
save 1
ukraine 1
today 1
cumpăraţi 1
acest 1
domeniu 1
copyright 1
rights 1
reserved 1
privacy 1
Google Preview Your look like this in google search result
SAVE-UKRAINE.TODAY
http://heroes.save-ukraine.today
Este posibil ca acest domeniu să fie de vânzare!
Page Size Code & Text Ratio
Document Size: ~14.35 KB
Code Size: ~2.14 KB
Text Size: ~12.21 KB Ratio: 85.11%

Estimation Traffic and Earnings

0
Unique Visits
Daily
0
Pages Views
Daily
$0
Income
Daily
0
Unique Visits
Monthly
0
Pages Views
Monthly
$0
Income
Monthly
0
Unique Visits
Yearly
0
Pages Views
Yearly
$0
Income
Yearly

Desktop

Desktop Screenshot
Time to Interactive 0.9 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Speed Index 0.9 s
Speed Index shows how quickly the contents of a page are visibly populated
Largest Contentful Paint 0.9 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
Network Round Trip Times 20 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
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
Largest Contentful Paint element 950 ms
This is the largest contentful element painted within the viewport
Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Uses efficient cache policy on static assets 2 resources found
A long cache lifetime can speed up repeat visits to your page
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Minimize third-party usage Third-party code blocked the main thread for 100 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
Reduce unused JavaScript Potential savings of 69 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Avoid long main-thread tasks 2 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Server Backend Latencies 50 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
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Does not use HTTPS 6 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Initial server response time was short Root document took 90 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 136 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoids an excessive DOM size 26 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)
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted

Mobile

Mobile Screenshot
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 3.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Largest Contentful Paint element 3,210 ms
This is the largest contentful element painted within the viewport
Server Backend Latencies 30 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
Network Round Trip Times 10 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
Serve static assets with an efficient cache policy 3 resources found
A long cache lifetime can speed up repeat visits to your page
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
Minimize third-party usage Third-party code blocked the main thread for 110 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
First Meaningful Paint 2.8 s
First Meaningful Paint measures when the primary content of a page is visible
Reduce unused JavaScript Potential savings of 69 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity
Serve images in next-gen formats Potential savings of 24 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Does not use HTTPS 6 insecure requests found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding [mixed content](https://developers.google.com/web/fundamentals/security/prevent-mixed-content/what-is-mixed-content), where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs
Document uses legible font sizes 89.87% 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
JavaScript execution time 1.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
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
Minimizes main-thread work 1.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Speed Index 2.8 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time 10 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids an excessive DOM size 24 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)
Avoids enormous network payloads Total size was 176 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 50 ms
Keep the server response time for the main document short because all other requests depend on it
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
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted
Time to Interactive 2.8 s
Time to Interactive is the amount of time it takes for the page to become fully interactive

Speed And Optimization Tips

Website speed has a huge impact on performance, affecting user experience, conversion rates and even rankings. ‪‬‬By reducing page load-times, users are less likely to get distracted and the search engines are more likely to reward you by ranking you
Title Website
Congratulations! Your title is optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Warning! Your site not have a robots.txt file
Sitemap.xml
Warning! Not found a sitemap file for your website
SSL Secure
Warning! Your website is not SSL secured (HTTPS).
Headings
Congratulations! You are using your H1 and H2 tags in your site
Blacklist
Congratulations! Your site is not listed in a blacklist
W3C Validator
Warning! Your site have errors W3C
Accelerated Mobile Pages (AMP)
Warning! Your site not have AMP Version
Domain Authority
Warning! Domain Authority of your website is slow. It is good to have domain authority more than 25.
GZIP Compress
Warning! Your site not is compressed, this can make slower response for the visitors
Favicon
Warning! Your site not have a favicon
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

0

Local Rank: / Users: / PageViews:

Global Rank

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Server: nginx
Date: Wed, 03 Jan 2024 13:48:32 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Buckets: bucket103
X-Adblock-Key: MFwwDQYJKoZIhvcNAQEBBQADSwAwSAJBALquDFETXRn0Hr05fUP7EJT77xYnPmRbpMy4vk8KYiHnkNpednjOANJcaXDXcKQJN0nXKZJL7TciJD8AoHXK158CAwEAAQ==_snxbuuQaUb+hhum1b1Gy2LS/afQXPVsgErEbZodeDR36zHNMqibIRmXAoQRr2KaUe1R8U4p/XK1JV3eWPyIBtw==
X-Template: tpl_CleanPeppermintBlack_twoclick
X-Language: romanian
Accept-CH: viewport-width
Accept-CH: dpr
Accept-CH: device-memory
Accept-CH: rtt
Accept-CH: downlink
Accept-CH: ect
Accept-CH: ua
Accept-CH: ua-full-version
Accept-CH: ua-platform
Accept-CH: ua-platform-version
Accept-CH: ua-arch
Accept-CH: ua-model
Accept-CH: ua-mobile
Accept-CH-Lifetime: 30
X-Domain: save-ukraine.today
X-Subdomain: heroes
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments