Your Website Score is

Similar Ranking

19
COASTAL MOTOR LODGE — MOTEL WITH ACCOMMODATION AND AMENITIES
coastalmotorlodge.co.nz
19
WHERE TO GO - BEST PLACES TO VISIT IN NZ
wheretogo.co.nz
19
LITTLE DREAM CAFE & RESTAURANT PARNELL - LITTLE DREAM CAFE & RESTAURANT PARNELL
littledream.nz
19
BLACK BOX PRODUCT REVIEWS
blackboxreviews.co.nz
19
BLACK BOX PRODUCT REVIEWS - READ AUTHENTIC CUSTOMER REVIEWS - BLACK BOX PRODUCT REVIEWS
blackboxreviews.com.au
14
BLACK BOX MARKET
blackboxmarket.co.nz
14
LIFE COACH | BUSINESS COACH | CORPORATE WORKSHOPS | BREE LE ROUX
breeleroux.com

Latest Sites

11
BRANDED MERCHANDISE MADE EASY! GIFTS | BRANDING | BRANDED APPARELPERSONALISED CORPORATE GIFTS | COMPANY BRANDED MERCHANDISE & APPAREL | PPE | BRANDED STATIONARY | BRANDED MERCHANDISE MADE EASY!
recogniseandreward.co.nz
19
BLACK BOX PRODUCT REVIEWS
blackboxreviews.co.nz
39
MOBILE PHONE REPAIR SERVICES | SCREEN REPLACEMENT | IPHONE REPAIR AUCKLAND
techpro.net.nz
14
LIFE COACH | BUSINESS COACH | CORPORATE WORKSHOPS | BREE LE ROUX
breeleroux.com
37
HOME ENERGY MANAGEMENT SERVICE | POWERGENIUS
powergenius.net
14
BLACK BOX MARKET
blackboxmarket.co.nz
34
WP USED CARS – JUST ANOTHER WORDPRESS SITE
wp.usedcarsforsale.nz

Top Technologies

CloudFlare
CDN
WordPress
CMS
Google Font API
Font Scripts
WooCommerce
Ecommerce
Font Awesome
Font Scripts
Shopify
Ecommerce
Bigcommerce
Ecommerce
LiteSpeed
Web Servers

19 littledream.nz Last Updated: 2 months

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

Desktop

Mobile

Performance Desktop Score 79%
Best Practices Desktop Score 86%
SEO Desktop Score 100%
Progressive Web App Desktop Score 30%
Performance Mobile Score 54%
Best Practices Mobile Score 79%
SEO Mobile Score 100%
Progressive Web App Mobile Score 57%
Page Authority Authority 10%
Domain Authority Domain Authority 6%
Moz Rank 1.0/10
Bounce Rate Rate 0%
Charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 87 Characters
LITTLE DREAM CAFE & RESTAURANT PARNELL - LITTLE DREAM CAFE & RESTAURANT PARNELL
Meta Description 122 Characters
Our Parnell cafe & restaurant was founded in 2018 on the principals of great coffee, great food and excellent service.
Effective URL 26 Characters
https://www.littledream.nz
Excerpt Page content
Little Dream Cafe & Restaurant Parnell - Little Dream Cafe & Restaurant Parnell Skip to content Call Us: 09 930 0080   96 St Georges Bay Road, ParnellLittle Dream Cafe & Restaurant ParnellBest Coffee! MenuHomeMenuFunctionsContac...
Keywords Cloud Density
menu10 little8 dream7 coffee6 great6 parnell6 cafe6 options6 food4 take4
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
menu 10
little 8
dream 7
coffee 6
great 6
parnell 6
cafe 6
options 6
food 4
take 4
Google Preview Your look like this in google search result
LITTLE DREAM CAFE & RESTAURANT PARNELL - LITTLE DREAM CA
https://www.littledream.nz
Our Parnell cafe & restaurant was founded in 2018 on the principals of great coffee, great food and excellent service.
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~63.92 KB
Code Size: ~32.36 KB
Text Size: ~31.55 KB Ratio: 49.37%

Estimation Traffic and Earnings

8
Unique Visits
Daily
14
Pages Views
Daily
$0
Income
Daily
224
Unique Visits
Monthly
399
Pages Views
Monthly
$0
Income
Monthly
2,592
Unique Visits
Yearly
4,704
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
Defer offscreen images Potential savings of 11 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Eliminate render-blocking resources Potential savings of 420 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Max Potential First Input Delay 250 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint 2.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Serve images in next-gen formats Potential savings of 229 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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Cumulative Layout Shift 0.032
Cumulative Layout Shift measures the movement of visible elements within the viewport
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Avoid long main-thread tasks 3 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Initial server response time was short Root document took 500 ms
Keep the server response time for the main document short because all other requests depend on it
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
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
Avoids an excessive DOM size 286 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)
Properly size images Potential savings of 275 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoids enormous network payloads Total size was 1,485 KiB
Large network payloads cost users real money and are highly correlated with long load times
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
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
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
Time to Interactive 1.6 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
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
First CPU Idle 1.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/).
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Remove unused CSS Potential savings of 91 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 static assets with an efficient cache policy 8 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid chaining critical requests 7 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
Page load is not fast enough on mobile networks Interactive on simulated mobile network at 11.0 s
A fast page load over a cellular network ensures a good mobile user experience
Keep request counts low and transfer sizes small 70 requests • 1,485 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Remove unused JavaScript Potential savings of 146 KiB
Remove unused JavaScript to reduce bytes consumed by network activity

Mobile

Mobile Screenshot
Initial server response time was short Root document took 400 ms
Keep the server response time for the main document short because all other requests depend on it
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 3.0 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G) 5835 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Avoid long main-thread tasks 10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Serve static assets with an efficient cache policy 8 resources found
A long cache lifetime can speed up repeat visits to your page
Remove unused CSS Potential savings of 93 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
Largest Contentful Paint 5.5 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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 9.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Serve images in next-gen formats Potential savings of 241 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
Reduce JavaScript execution time 2.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 69 requests • 1,396 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Properly size images Potential savings of 90 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Speed Index 4.5 s
Speed Index shows how quickly the contents of a page are visibly populated
Avoids enormous network payloads Total size was 1,396 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
First CPU Idle 7.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/).
First Meaningful Paint 3.1 s
First Meaningful Paint measures when the primary content of a page is visible
Cumulative Layout Shift 0.049
Cumulative Layout Shift measures the movement of visible elements within the viewport
Total Blocking Time 450 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Avoids an excessive DOM size 286 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)
Document uses legible font sizes 99.61% 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 JavaScript Potential savings of 146 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Minimize third-party usage Third-party code blocked the main thread for 120 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
Estimated Input Latency 130 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
Defer offscreen images Potential savings of 11 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
Max Potential First Input Delay 560 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoid chaining critical requests 8 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
Eliminate render-blocking resources Potential savings of 1,890 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles

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
Warning! Your title is not optimized
Description Website
Congratulations! Your description is optimized
Robots.txt
Congratulations! Your site have a robots.txt file
Sitemap.xml
Congratulations! We've found a sitemap file for your website
SSL Secure
Congratulations! Your site have Support to 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
Congratulations! Your website appears to have a favicon.
Broken Links
Congratulations! You not have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Thu, 24 Sep 2020 04:29:12 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=dd018cac4dee0ff7b8b677245154769ba1600921752; expires=Sat, 24-Oct-20 04:29:12 GMT; path=/; domain=.littledream.nz; HttpOnly; SameSite=Lax
Vary: Accept-Encoding
Vary: Accept-Encoding
Last-Modified: Tue, 15 Sep 2020 21:19:14 GMT
Cache-Control: max-age=0
Expires: Thu, 24 Sep 2020 04:29:12 GMT
CF-Cache-Status: DYNAMIC
cf-request-id: 055ff86c400000d695a680a200000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 5d79c35a0870d695-SYD
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records