Your Website Score is

Similar Ranking

55
ETORO - THE WORLD’S LEADING SOCIAL TRADING AND INVESTING PLATFORM
etoro.com
55
SCIENTIFIC RESEARCH PUBLISHING
scirp.org
55
UNITED STATES COURTS |
uscourts.gov
55
JOE MONSTER.ORG - PROBABLY THE BEST PAGE IN THE UNIVERSE
joemonster.org
55
--- ROCK - ONLINE --- READER
---rock.com
55
BULBAGARDEN: THE ORIGINAL POKÉMON COMMUNITY
bulbagarden.net
55
CHARLES SCHWAB | A MODERN APPROACH TO INVESTING & RETIREMENT
schwab.com

Latest Sites

36
CASINO REVIEWS AND GAME BONUSES - JENNYCASINO.COM
jennycasino.com
54
AMAZON.COM
amazon.com
6
LOGIN | POWER OF DREAM
powerofdream.co.id
7
BITMINEROPTIONS
bitmineroptions.com
7
欢迎访问本网站
gtr.com
19
OMEGAPRO FOREX
omegaprofx.com
5
LUXCITI : TIENDA ONLINE DE PRODUCTOS DE PELUQUERÍA, COMPRAS ONLINE ESPAÑA
luxciti.es

Top Technologies

Nginx
Web Servers
PHP
Programming Languages
Google Tag Manager
Tag Managers
Google Font API
Font Scripts
CloudFlare
CDN
jQuery
JavaScript Frameworks
Apache
Web Servers
Font Awesome
Font Scripts
WordPress
CMS
Twitter Bootstrap
Web Frameworks

55 tray.com.br Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 92%
Best Practices Desktop Score 69%
SEO Desktop Score 91%
Progressive Web App Desktop Score 31%
Performance Mobile Score 59%
Best Practices Mobile Score 69%
SEO Mobile Score 92%
Progressive Web App Mobile Score 59%
Page Authority Authority 44%
Domain Authority Domain Authority 72%
Moz Rank 4.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 64 Characters
TRAY | PLATAFORMA DE E-COMMERCE COMPLETA PARA CRIAR LOJA VIRTUAL
Meta Description 244 Characters
Com 15 anos de história e mais de 200 integrações a Tray é a Plataforma de E-commerce completa, para quem deseja criar uma loja virtual profissional integrada aos maiores marketplaces e serviços. Suporte telefônico para você nunca ficar na mão.
Effective URL 23 Characters
https://www.tray.com.br
Excerpt Page content
Tray | Plataforma de E-commerce Completa Para Criar Loja Virtual ...
Keywords Cloud Density
para41 loja41 você21 tray21 mais20 grátis19 virtual15 integração14 mail13 mercado12
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
para 41
loja 41
você 21
tray 21
mais 20
grátis 19
virtual 15
integração 14
mail 13
mercado 12
Google Preview Your look like this in google search result
TRAY | PLATAFORMA DE E-COMMERCE COMPLETA PARA CRIAR LOJA VIR
https://www.tray.com.br
Com 15 anos de história e mais de 200 integrações a Tray é a Plataforma de E-commerce completa, para quem deseja criar uma loja virtual profissional i
Robots.txt File Detected
http://tray.com.br/robots.txt
Sitemap.xml File Detected
http://tray.com.br/sitemap.xml
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: 2027-07-24 / 79 months 7 days

TRAY TECNOLOGIA EM E-COMMERCE LTDA ,BR BR
Registrar Email: [email protected]

Nameservers
ns-2038.awsdns-62.co.uk
ns-1303.awsdns-34.org
ns-153.awsdns-19.com
ns-588.awsdns-09.net
Page Size Code & Text Ratio
Document Size: ~110.21 KB
Code Size: ~61.87 KB
Text Size: ~48.33 KB Ratio: 43.86%

Estimation Traffic and Earnings

Only Registered Users

Sign up for see all features and reviews about this site

Login

Technologies

PWA - Manifest

Manifest is not valid
Your site don't have valid manifest.json, read more in Web App Manifest

Desktop

Desktop Screenshot
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 10.2 s
A fast page load over a cellular network ensures a good mobile user experience
Estimated Input Latency 10 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
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
Serve images in next-gen formats Potential savings of 320 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
Reduce server response times (TTFB) Root document took 1,090 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 69 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 13 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
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
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.0 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 53 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 88 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.7 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 0.9 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,675 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 0.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 0.8 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 32 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,083 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 Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 126 requests • 1,675 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 96 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 40 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 0.9 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

Mobile

Mobile Screenshot
Total Blocking Time 160 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
JavaScript execution time 0.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Defer offscreen images Potential savings of 588 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
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
Properly size images Potential savings of 109 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.8 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).
Avoids enormous network payloads Total size was 1,348 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 2.3 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.1 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 2 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 30 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,083 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 Meaningful Paint 3.3 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 120 requests • 1,348 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 87 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 140 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 9.3 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
First Contentful Paint (3G) 6582 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 10 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
Minify CSS Potential savings of 3 KB
Minifying CSS files can reduce network payload sizes
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
Document uses legible font sizes 99.1% 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
Serve images in next-gen formats Potential savings of 243 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
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 1,080 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 69 KB
Optimized images load faster and consume less cellular data
Enable text compression Potential savings of 13 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes
Minimize third-party usage Third-party code blocked the main thread for 60 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

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
Server: nginx
Date: Tue, 14 Jan 2020 17:30:07 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Link: ; rel="https://api.w.org/"
Link: ; rel=shortlink
Access-Control-Allow-Origin: *
access_ip: 177.67.118.195
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A tray.com.br 177.67.118.70 IN 3534
NS tray.com.br ns-153.awsdns-19.com IN 52104
NS tray.com.br ns-1303.awsdns-34.org IN 52104
NS tray.com.br ns-588.awsdns-09.net IN 52104
NS tray.com.br ns-2038.awsdns-62.co.uk IN 52104
MX tray.com.br alt2.aspmx.l.google.com IN 3600
MX tray.com.br aspmx3.googlemail.com IN 3600
MX tray.com.br aspmx.l.google.com IN 3600
MX tray.com.br aspmx2.googlemail.com IN 3600
MX tray.com.br alt1.aspmx.l.google.com IN 3600
TXT tray.com.br kBZVrKy3QBFN+W8qPA13BWqyHYwsJGgPBGXk5h9dxjg= IN 15

Comments

Copyright © 2019 Check.web.id | Privacy Policy | Terms and Conditions
Languages | Bahasa Deutsch English Español Français Nederlands Português Pусский
Add extension to Chrome