Your Website Score is

Similar Ranking

87
.NET |---. CROSS-PLATFORM. OPEN SOURCE.
windows.net
87
CCM - ONLINE COMMUNITY
ccm.net
87
GOOGLE
google.fi
87
東洋経済オンライン | 経済ニュースの新基準
toyokeizai.net
87
店铺浏览-淘宝网
janeeyre.tmall.com
87
COMO CRIAR UM SITE GRÁTIS | DESCUBRA COMO CRIAR UM SITE GRÁTIS - WEBNODE
webnode.com.br
87
WELCOME TO PYTHON.ORG
python.org

Latest Sites

23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.com
86
MEGOGO.NET - ФИЛЬМЫ И ТЕЛЕКАНАЛЫ ОНЛАЙН
megogo.net
59
MANOMANO : A--- EN LIGNE BRICOLAGE, RÉNOVATION ET JARDINAGE
manomano.fr
91
TECHTUDO - A TECNOLOGIA DESCOMPLICADA.
techtudo.com.br
70
AGILE PROJECT MANAGEMENT | PIVOTAL TRACKER
pivotaltracker.com
31
MOTORPLUS - PORTAL BERITA MOTOR PERTAMA DAN TERKINI
motorplus-online.com

Top Technologies

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

87 suamusica.com.br Last Updated: 9 months

Success 70% of passed verification steps
Warning 15% of total warning
Errors 15% of total errors, require fast action

Desktop

Mobile

Performance Desktop Score 26%
Best Practices Desktop Score 62%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 25%
Best Practices Mobile Score 54%
SEO Mobile Score 85%
Progressive Web App Mobile Score 33%
Page Authority Authority 47%
Domain Authority Domain Authority 89%
Moz Rank 4.7/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 10 Characters
SUA MÚSICA
Meta Description 238 Characters
Baixe grátis na melhor plataforma de lançamento de Artistas independentes do Brasil. Shows, CDs Promocionais, Músicas, Vídeo Clipes, Instagram e novidades do Forró, Sertanejo, Axé e outros. Crie um Pefil grátis para sua Banda agora mesmo.
Effective URL 24 Characters
https://suamusica.com.br
Excerpt Page content
Sua Música ...
Keywords Cloud Density
música42 vivo13 wesley13 safadão12 total12 promocional10 vaqueiro10 fellipe9 márcia9 todos9
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
música 42
vivo 13
wesley 13
safadão 12
total 12
promocional 10
vaqueiro 10
fellipe 9
márcia 9
todos 9
Google Preview Your look like this in google search result
SUA MÚSICA
https://suamusica.com.br
Baixe grátis na melhor plataforma de lançamento de Artistas independentes do Brasil. Shows, CDs Promocionais, Músicas, Vídeo Clipes, Instagram e novid
Robots.txt File Detected
Sitemap.xml File Detected
Whois Is a query and response protocol that is widely used for querying databases that store the registered users or assignees of an Internet resource, such as a domain name, an IP address block, or an autonomous system
Updated: 1970-01-01 / 51 years
Create on: 1970-01-01 / 51 years
Expires on: 2023-12-29 / 39 months 26 days

Ambi Servi�os de Internet Ltda. ,BR BR
Registrar Email: [email protected]

Nameservers
ns-711.awsdns-24.net
ns-272.awsdns-34.com
ns-1777.awsdns-30.co.uk
ns-1381.awsdns-44.org
Page Size Code & Text Ratio
Document Size: ~156.15 KB
Code Size: ~108.67 KB
Text Size: ~47.48 KB Ratio: 30.41%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Sua Música SuaMusica

The web app manifest is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in areas where they would expect to see apps (for example, a mobile device's home screen)
Param name
Sua Música
Param short_name
SuaMusica
Param start_url
/
Param display
standalone
Param gcm_sender_id
103953800507
Param gcm_user_visible_only
1
Manifest is not valid
Your manifest are missing some important params, read more in Web App Manifest

Desktop

Desktop Screenshot
Reduce server response times (TTFB) Root document took 920 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 650 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 29 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 720 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
Total Blocking Time 370 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 2.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 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
Defer offscreen images Potential savings of 2,911 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Properly size images Potential savings of 80 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 6.2 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoid enormous network payloads Total size was 6,652 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 5.0 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 1.3 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 65 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 an excessive DOM size 1,899 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)
Minify JavaScript Potential savings of 16 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 1.4 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 468 requests • 6,652 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 85 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 200 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 8.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Network Round Trip Times 0 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 41.5 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 60 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Remove unused CSS Potential savings of 239 KB
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
Serve images in next-gen formats Potential savings of 569 KB
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
User Timing marks and measures 9 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences

Mobile

Mobile Screenshot
Document uses legible font sizes 73.11% 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
Remove unused CSS Potential savings of 163 KB
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
Uses deprecated APIs 1 warning found
Deprecated APIs will eventually be removed from the browser
Serve images in next-gen formats Potential savings of 76 KB
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
User Timing marks and measures 2 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Reduce server response times (TTFB) Root document took 600 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 2,210 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Enable text compression Potential savings of 124 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Reduce the impact of third-party code Third-party code blocked the main thread for 540 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
Total Blocking Time 980 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Reduce JavaScript execution time 3.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Server Backend Latencies 0 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
Defer offscreen images Potential savings of 76 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Speed Index 10.3 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 12.7 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. [Learn more](https://web.dev/first-cpu-idle).
Avoids enormous network payloads Total size was 1,688 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 6.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted
Includes front-end JavaScript libraries with known security vulnerabilities 4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 13 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
Avoids an excessive DOM size 462 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)
Minify JavaScript Potential savings of 19 KB
Minifying JavaScript files can reduce payload sizes and script parse time
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 166 requests • 1,688 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Serve static assets with an efficient cache policy 36 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 14.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Links do not have descriptive text 2 links found
Descriptive link text helps search engines understand your content
Network Round Trip Times 0 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
Page load is not fast enough on mobile networks Interactive at 14.5 s
A fast page load over a cellular network ensures a good mobile user experience
First Contentful Paint (3G) 6789 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Estimated Input Latency 60 ms
Estimated Input Latency is an estimate of how long your app takes to respond to user input, in milliseconds, during the busiest 5s window of page load. If your latency is higher than 50 ms, users may perceive your app as laggy
Tap targets are sized appropriately 100% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements

Speed And Optimization Tips

Only Registered Users

Sign up for see all features and reviews about this site

Login

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
Content-Type: text/html; charset=UTF-8
Content-Length: 0
Connection: keep-alive
Server: awselb/2.0
Date: Mon, 09 Dec 2019 12:01:14 GMT
pragma: no-cache
cache-control: no-store, no-cache, must-revalidate
expires: Thu, 19 Nov 1981 08:52:00 GMT
set-cookie: SMSession=m3jiou3a1fakrdkj3sfh4n75ok; expires=Wed, 08-Jan-2020 12:01:13 GMT; Max-Age=2592000; path=/; domain=.suamusica.com.br; secure; HttpOnly
x-powered-by: PHP/7.2.15
X-Cache: Miss from cloudfront
Via: 1.1 6afc1c7b9e6d4dbe30a0b3eae05d0f9e.cloudfront.net (CloudFront)
X-Amz-Cf-Pop: EWR52-C4
X-Amz-Cf-Id: ZwiuCjHdU7x_0pjeIRKCla9OSy-nH5lF_oLBu4YjKtgsQRrX1mMFwg==
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome