Your Website Score is

Similar Ranking

2
PIZZA ROMA ROYAN
pizzaromaroyan.fr
2
MAMAPAPA FORUM КИЕВ 2022 16 АПРЕЛЯ – СЕМИНАР-ЛЕКЦИИ ДЛЯ РОДИТЕЛЕЙ О ВОСПИТАНИИ ДЕТЕЙ
mamapapa.in.ua
1
appletshirtus.com
1
fitness.gr.com
1
fsgratis.com
1
favicon.ico
1
replicajerseys1111.com

Latest Sites

1
-
xxvideo.skin
1
-
granny.work
1
-
tube8.icu
1
-
nudegirls.yachts
1
-
gaysessotube.info
19
CORVUS BEDRIJFSRECHERCHE - CORVUS | RECHERCHEBUREAU CORVUS BV | NIEUWEGEIN
corvusbv.nl
38
ТАНЫ ТЕЛЕВИЗ TV9
tv9.mn

Top Technologies

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

2 pizzaromaroyan.fr Last Updated: 5 years

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

Desktop

Mobile

Performance Desktop Score 83%
Best Practices Desktop Score 79%
SEO Desktop Score 80%
Progressive Web App Desktop Score 11%
Performance Mobile Score 69%
Best Practices Mobile Score 86%
SEO Mobile Score 83%
Progressive Web App Mobile Score 39%
Page Authority Authority 0%
Domain Authority Domain Authority 0%
Moz Rank 0.0/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 16 Characters
PIZZA ROMA ROYAN
Meta Description 0 Characters
NO DATA
Effective URL 24 Characters
http://pizzaromaroyan.fr
Excerpt Page content
Pizza Roma Royan ...
Keywords Cloud Density
18h306 11h305 14h305 22h004 saint3 royan3 22h302 coin2 pizzas2 contact2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
18h30 6
11h30 5
14h30 5
22h00 4
saint 3
royan 3
22h30 2
coin 2
pizzas 2
contact 2
Google Preview Your look like this in google search result
PIZZA ROMA ROYAN
http://pizzaromaroyan.fr
Pizza Roma Royan ...
Robots.txt File No Found
http://pizzaromaroyan.fr/robots.txt
Sitemap.xml File No Found
http://pizzaromaroyan.fr/sitemap.xml
Page Size Code & Text Ratio
Document Size: ~13.68 KB
Code Size: ~9.24 KB
Text Size: ~4.44 KB Ratio: 32.47%

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

Technologies

Only Registered Users

Sign up for see all features and reviews about this site

Login

PWA - Manifest

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

Desktop

Desktop Screenshot
Remove unused JavaScript Potential savings of 454 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
Cumulative Layout Shift 0.065
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint 0.9 s
First Contentful Paint marks the time at which the first text or image is painted
Efficiently encode images Potential savings of 33 KiB
Optimized images load faster and consume less cellular data
First CPU Idle 2.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/).
Keep request counts low and transfer sizes small 67 requests • 2,133 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
JavaScript execution time 0.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Properly size images Potential savings of 206 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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 20 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
Eliminate render-blocking resources Potential savings of 130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
Remove unused CSS Potential savings of 73 KiB
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 544 KiB
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
Avoid chaining critical requests 22 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
Does not use HTTPS 33 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 servedover 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
Max Potential First Input Delay 160 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Initial server response time was short Root document took 130 ms
Keep the server response time for the main document short because all other requests depend on it
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Avoids large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Time to Interactive 3.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 0.9 s
First Meaningful Paint measures when the primary content of a page is visible
Avoids an excessive DOM size 171 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 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 240 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
Minimizes main-thread work 1.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
User Timing marks and measures 4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Speed Index 1.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Serve static assets with an efficient cache policy 35 resources found
A long cache lifetime can speed up repeat visits to your page
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 15.4 s
A fast page load over a cellular network ensures a good mobile user experience
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids enormous network payloads Total size was 2,133 KiB
Large network payloads cost users real money and are highly correlated with long load times
Largest Contentful Paint 1.8 s
Largest Contentful Paint marks the time at which the largest text or image is painted

Mobile

Mobile Screenshot
Avoid serving legacy JavaScript to modern browsers Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers
First Meaningful Paint 4.4 s
First Meaningful Paint measures when the primary content of a page is visible
Efficiently encode images Potential savings of 33 KiB
Optimized images load faster and consume less cellular data
Does not use HTTPS 31 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 servedover 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
Estimated Input Latency 40 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
Properly size images Potential savings of 40 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Largest Contentful Paint 4.6 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid long main-thread tasks 7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
First Contentful Paint 3.1 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce the impact of third-party code Third-party code blocked the main thread for 390 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
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
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
Max Potential First Input Delay 170 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
First CPU Idle 5.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/).
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 (3G) 6420 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Total Blocking Time 290 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoids enormous network payloads Total size was 1,391 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 10 ms
Keep the server response time for the main document short because all other requests depend on it
Cumulative Layout Shift 0.031
Cumulative Layout Shift measures the movement of visible elements within the viewport
Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve static assets with an efficient cache policy 32 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 22 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
Remove unused CSS Potential savings of 24 KiB
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
JavaScript execution time 1.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Keep request counts low and transfer sizes small 50 requests • 1,391 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Eliminate render-blocking resources Potential savings of 150 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 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
Time to Interactive 6.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 167 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 large JavaScript libraries with smaller alternatives 0 large libraries found
Large JavaScript libraries can lead to poor performance. Prefer smaller, functionally equivalent libraries to reduce your bundle size
Serve images in next-gen formats Potential savings of 544 KiB
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
Remove unused JavaScript Potential savings of 43 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

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
Warning! Your description is not 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
Warning! Your page not contain any H1 and H2 headings. H1 and H2 headings help indicate the important topics of your page to search engines
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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links
First 4 Links Relationship HTTP Status
http://pizzaromaroyan.fr/index.html Internal Link 200
Nos Pizzas Internal Link 200
Coin Snack (le midi) Internal Link 200
Notre Carte Internal Link 200

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
Server: GitHub.com
Last-Modified: Fri, 11 Dec 2020 16:53:38 GMT
ETag: W/"5fd3a412-36a1"
Access-Control-Allow-Origin: *
Expires: Fri, 11 Dec 2020 18:34:21 GMT
Cache-Control: max-age=600
Content-Encoding: gzip
X-Proxy-Cache: MISS
X-GitHub-Request-Id: 48FA:5E59:64C94:6B5D2:5FD3B955
Content-Length: 3391
Accept-Ranges: bytes
Date: Fri, 11 Dec 2020 18:24:21 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-fra19136-FRA
X-Cache: HIT
X-Cache-Hits: 1
X-Timer: S1607711062.537839,VS0,VE1
Vary: Accept-Encoding
X-Fastly-Request-ID: 653b0e09a98bfb5536f3477378dbf80bc685d07e
DNS Records DNS Resource Records associated with a hostname
View DNS Records
Type Name Value Class TTL
A pizzaromaroyan.fr 185.199.109.153 IN 3598
A pizzaromaroyan.fr 185.199.108.153 IN 3598
A pizzaromaroyan.fr 185.199.111.153 IN 3598
A pizzaromaroyan.fr 185.199.110.153 IN 3598
NS pizzaromaroyan.fr ns-uk.topdns.com IN 3600
NS pizzaromaroyan.fr ns-usa.topdns.com IN 3600
NS pizzaromaroyan.fr ns-canada.topdns.com IN 3600

Comments

About Us

Check your website stats, All-In-One SEO Stats, improve SEO of your website. Generate professional SEO reports for your clients.

Contact Info

SEOSiteStats.com
contact@seositestats.com

Follow Us

Facebook
© SEO Site Stats 2020
Languages | English Română