Your Website Score is

Similar Ranking

53
MENSAGENS COM AMOR. FRASES E MENSAGENS DE AMOR QUE FALAM POR VOCÊ.
mensagenscomamor.com
53
POSTMATES: FOOD DELIVERY, GROCERIES, ALCOHOL - ANYTHING FROM ANYWHERE
postmates.com
53
3D CAD DESIGN SOFTWARE | SOLIDWORKS
solidworks.com
53
AKAM - HABERLER - SON DAKIKA HABERLERI
aksam.com.tr
53
RECRUITING SOFTWARE | LEVER
lever.co
53
お知らせ - ZOZOTOWN
zozo.jp
53
CDMX - PORTAL CIUDADANO
cdmx.gob.mx

Latest Sites

24
THIẾT KẾ - THI CÔNG NỘI THẤT - SẢN XUẤT TRỰC TIẾP | NỘI THẤT MẠNH HỆ
noithatmanhhe.vn
19
SẢN PHẨM NỘI THẤT: GIƯỜNG TẦNG, GIƯỜNG BÀN, GIƯỜNG GẤP
nhacanhothongminh.com
16
CRYPTO-MINING.BIZ - REGISTERED AT NAMECHEAP.COM
crypto-mining.biz
57
99.9% DICE - BITCOIN, DOGECOIN, LITECOIN & ETHEREUM GAMBLING
999dice.com
19
RELANDICE BOT FOR 999DICE
relandice.com
23
❶ BẢO PHONG | LẮP ĐẶT CAMERA, CAMERA WIFI GIÁ RẺ Ở HUẾ !
baophong.vn
51
ONE MORE STEP
seeking.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

53 yelp.ca Last Updated: 9 months

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

Desktop

Mobile

Performance Desktop Score 95%
Best Practices Desktop Score 62%
SEO Desktop Score 73%
Progressive Web App Desktop Score 46%
Performance Mobile Score 66%
Best Practices Mobile Score 77%
SEO Mobile Score 85%
Progressive Web App Mobile Score 56%
Page Authority Authority 54%
Domain Authority Domain Authority 67%
Moz Rank 5.4/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 68 Characters
CHARLOTTE RESTAURANTS, DENTISTS, BARS, BEAUTY SALONS, DOCTORS - YELP
Meta Description 126 Characters
Charlotte - User Reviews and Recommendations of Top Restaurants, Shopping, Nightlife, Entertainment, Services and More at Yelp
Effective URL 35 Characters
https://www.yelp.ca/charlotte-nc-us
Excerpt Page content
Charlotte Restaurants, Dentists, Bars, Beauty Salons, Doctors - Yelp ...
Keywords Cloud Density
yelp23 click20 search20 page14 address13 english13 near13 location12 city11 again11
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
yelp 23
click 20
search 20
page 14
address 13
english 13
near 13
location 12
city 11
again 11
Google Preview Your look like this in google search result
CHARLOTTE RESTAURANTS, DENTISTS, BARS, BEAUTY SALONS, DOCTOR
https://www.yelp.ca/charlotte-nc-us
Charlotte - User Reviews and Recommendations of Top Restaurants, Shopping, Nightlife, Entertainment, Services and More at Yelp
Robots.txt File No Found
Sitemap.xml File No Found
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: 2018-06-15 / 2 years
Create on: 2006-07-17 / 14 years
Expires on: 2020-07-17 / 2 months 7 days

MarkMonitor International Canada Ltd. ,US
Registrar Name: Yelp Inc. TMA 858370
Registrar Whois Server: whois.ca.fury.ca
Registrar URL: Markmonitor.com
Registrar Phone: +1.4159083801
Registrar Email: [email protected]
Registrar Address: 140 New Montgomery,9th Floor , San Francisco

Laurence Wilson
Admin Organization: Yelp Inc. TMA 858370
Admin Email: [email protected]
Admin Phone: +1.4159083801
Admin Address: 140 New Montgomery, 9th Floor, San Francisco

Nameservers
dns1.p03.nsone.net
dns2.p03.nsone.net
dns3.p03.nsone.net
ns03.midtowndoornailns.com
ns04.midtowndoornailns.com
ns02.midtowndoornailns.com
dns4.p03.nsone.net
ns01.midtowndoornailns.com
Page Size Code & Text Ratio
Document Size: ~150.19 KB
Code Size: ~114.74 KB
Text Size: ~35.45 KB Ratio: 23.60%

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
First CPU Idle 1.6 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,639 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimizes main-thread work 1.2 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.6 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 3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
Avoid chaining critical requests 6 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 6,134 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.6 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 94 requests • 1,639 KB
To set budgets for the quantity and size of page resources, add a budget.json file
Uses efficient cache policy on static assets 1 resource found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 2.0 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
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
Remove unused CSS Potential savings of 55 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 157 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 970 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Minimize third-party usage Third-party code blocked the main thread for 10 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 90 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
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
Defer offscreen images Potential savings of 418 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 462 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated

Mobile

Mobile Screenshot
Total Blocking Time 1,030 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.0 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 11 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 11 KB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 3.6 s
Speed Index shows how quickly the contents of a page are visibly populated
First CPU Idle 7.0 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 527 KB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First Contentful Paint 2.8 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid chaining critical requests 5 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 333 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 2.8 s
First Meaningful Paint measures when the primary content of a page is visible
Keep request counts low and transfer sizes small 43 requests • 527 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 3 resources found
A long cache lifetime can speed up repeat visits to your page
Max Potential First Input Delay 460 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task
Time to Interactive 7.7 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) 5490 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 140 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
Document uses legible font sizes 100% 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 28 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
Avoid multiple page redirects Potential savings of 780 ms
Redirects introduce additional delays before the page can be loaded
Server response times are low (TTFB) Root document took 510 ms
Time To First Byte identifies the time at which your server sends a response
Eliminate render-blocking resources Potential savings of 300 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Reduce the impact of third-party code Third-party code blocked the main thread for 350 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
Content-Type: text/html; charset=UTF-8
cache-control: max-age=0, must-revalidate, no-cache, no-store, private, no-transform
pragma: no-cache
set-cookie: pid=; Domain=.yelp.ca; Max-Age=0; Path=/; expires=Wed, 31-Dec-97 23:59:59 GMT
set-cookie: bse=e744937fe24947b0a709227e4185ef7b; Domain=.yelp.ca; Path=/; HttpOnly
set-cookie: location=%7B%22city%22%3A+%22Charlotte%22%2C+%22state%22%3A+%22NC%22%2C+%22country%22%3A+%22US%22%2C+%22latitude%22%3A+35.2253407570904%2C+%22longitude%22%3A+-80.84537520117186%2C+%22max_latitude%22%3A+35.346418%2C+%22min_latitude%22%3A+35.045918%2C+%22max_longitude%22%3A+-80.710628%2C+%22min_longitude%22%3A+-80.94991%2C+%22zip%22%3A+%22%22%2C+%22address1%22%3A+%22%22%2C+%22address2%22%3A+%22%22%2C+%22address3%22%3A+null%2C+%22neighborhood%22%3A+null%2C+%22borough%22%3A+null%2C+%22provenance%22%3A+%22YELP_GEOCODING_ENGINE%22%2C+%22display%22%3A+%22Charlotte%2C+NC%2C+United+States%22%2C+%22unformatted%22%3A+%22Charlotte%2C+NC%2C+United+States%22%2C+%22isGoogleHood%22%3A+null%2C+%22usingDefaultZip%22%3A+null%2C+%22accuracy%22%3A+4.0%2C+%22language%22%3A+null%7D; Domain=.yelp.ca; Max-Age=630720000; Path=/; expires=Mon, 05-Dec-2039 15:45:10 GMT
set-cookie: hl=en_CA; Domain=.yelp.ca; Max-Age=630720000; Path=/; expires=Mon, 05-Dec-2039 15:45:11 GMT
set-cookie: wdi=1|0C91F70417739EA6|0x1.77bef61a35254p+30|7f73c35987bacd2c; Domain=.yelp.ca; Path=/; Max-Age=630720000; Expires=Mon, 05 Dec 2039 15:45:11 GMT; HttpOnly
strict-transport-security: max-age=31536000; includeSubDomains; preload
expires: Tue, 10 Dec 2019 15:45:10 GMT
x-node: www_all
x-node: 10-65-140-217-useast1bprod-6c503f7f-1b55-11ea-81ab-0247530d1
x-xss-protection: 1; report=https://www.yelp.com/xss_protection_report
x-b3-sampled: 0
x-content-type-options: nosniff
content-security-policy-report-only: report-uri https://www.yelp.com/csp_report_only?page=csp_report_frame_directives_full_site_ssl_csp_report_directives&site=www; frame-ancestors 'self' https://*.yelp.com; default-src https:; img-src https: data: https://*.adsrvr.org; script-src https: 'unsafe-inline' 'unsafe-eval' blob:; style-src https: 'unsafe-inline' data:; connect-src https:; font-src 'self' https://*.yelpcdn.com https://fonts.gstatic.com https://connect.facebook.net https://cdnjs.cloudflare.com https://apis.google.com https://www.google-analytics.com; frame-src https: yelp-webview://* yelp://* data:; child-src https: yelp-webview://* yelp://*; media-src https:; object-src 'none'; base-uri 'self'; form-action https: 'self'
x-zipkin-id: ab4eec5244082edb
x-routing-service: 10-65-175-47-useast1bprod; site=www
referrer-policy: origin-when-cross-origin
x-mode: ro
x-proxied: 10-65-163-96-useast1bprod
content-encoding: gzip
Accept-Ranges: bytes
Transfer-Encoding: chunked
Accept-Ranges: bytes
Date: Tue, 10 Dec 2019 15:45:11 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-jfk8140-JFK
X-Cache: MISS
X-Cache-Hits: 0
X-Timer: S1575992711.546970,VS0,VE632
Vary: User-Agent, Accept-Encoding
DNS Records DNS Resource Records associated with a hostname
View DNS Records

Comments

Add extension to Chrome