Your Website Score is

Similar Ranking

39
MASSEY PHYSIOTHERAPY, WEST AUCKLAND PHYSIO, FRIENDLY AND EXPERIENCED
masseyphysio.co.nz
39
SMASHED PUMPKIN CAFE WESTGATE
smashedpumpkincafe.co.nz
39
MOBILE PHONE REPAIR SERVICES | SCREEN REPLACEMENT | IPHONE REPAIR AUCKLAND
techpro.net.nz
37
HOME ENERGY MANAGEMENT SERVICE | POWERGENIUS
powergenius.net
34
WP USED CARS – JUST ANOTHER WORDPRESS SITE
wp.usedcarsforsale.nz
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

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
YouTube
Video Players
Nginx
Web Servers

39 smashedpumpkincafe.co.nz Last Updated: 2 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 80%
Best Practices Desktop Score 86%
SEO Desktop Score 100%
Progressive Web App Desktop Score 56%
Performance Mobile Score 62%
Best Practices Mobile Score 79%
SEO Mobile Score 100%
Progressive Web App Mobile Score 57%
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 29 Characters
SMASHED PUMPKIN CAFE WESTGATE
Meta Description 76 Characters
Our Westgate cafe has great coffee and delicious food. Dine in or take away.
Effective URL 36 Characters
https://www.smashedpumpkincafe.co.nz
Excerpt Page content
Smashed Pumpkin Cafe Westgate Skip to content Call Us: 09-833 8016  19 Fernhill Dr, Massey, Waitakere 0614Smashed Pumpkin Cafe WestgateBest Coffee and Food! MenuHomeMenuOrder OnlineFoodBreakfastLunchSnacksChildren’s MenuCoffeeCartCheckou...
Google Preview Your look like this in google search result
SMASHED PUMPKIN CAFE WESTGATE
https://www.smashedpumpkincafe.co.nz
Our Westgate cafe has great coffee and delicious food. Dine in or take away.
Page Size Code & Text Ratio
Document Size: ~53.1 KB
Code Size: ~26.23 KB
Text Size: ~26.88 KB Ratio: 50.61%

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
Time to Interactive 2.2 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Avoids an excessive DOM size 271 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)
Remove unused JavaScript Potential savings of 179 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
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
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
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
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted
Eliminate render-blocking resources Potential savings of 440 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Total Blocking Time 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Properly size images Potential savings of 182 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Speed Index 2.4 s
Speed Index shows how quickly the contents of a page are visibly populated
Serve images in next-gen formats Potential savings of 298 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
Max Potential First Input Delay 240 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids enormous network payloads Total size was 1,638 KiB
Large network payloads cost users real money and are highly correlated with long load times
First CPU Idle 1.5 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/).
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
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
Serve static assets with an efficient cache policy 15 resources found
A long cache lifetime can speed up repeat visits to your page
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
Keep request counts low and transfer sizes small 72 requests • 1,638 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Defer offscreen images Potential savings of 60 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive
First Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Largest Contentful Paint 2.0 s
Largest Contentful Paint marks the time at which the largest text or image is painted
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
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
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
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
Cumulative Layout Shift 0.034
Cumulative Layout Shift measures the movement of visible elements within the viewport
Initial server response time was short Root document took 600 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

Mobile

Mobile Screenshot
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/).
Eliminate render-blocking resources Potential savings of 1,730 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Largest Contentful Paint 3.3 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
Avoid long main-thread tasks 9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Document uses legible font sizes 99.19% 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
Initial server response time was short Root document took 230 ms
Keep the server response time for the main document short because all other requests depend on it
Avoids enormous network payloads Total size was 1,250 KiB
Large network payloads cost users real money and are highly correlated with long load times
Minimize main-thread work 3.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Serve images in next-gen formats Potential savings of 127 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
Time to Interactive 8.4 s
Time to interactive is the amount of time it takes for the page to become fully interactive
Properly size images Potential savings of 110 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
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
Avoids an excessive DOM size 272 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)
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
Remove unused JavaScript Potential savings of 183 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Serve static assets with an efficient cache policy 16 resources found
A long cache lifetime can speed up repeat visits to your 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
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
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
Keep request counts low and transfer sizes small 73 requests • 1,250 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
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
Speed Index 5.0 s
Speed Index shows how quickly the contents of a page are visibly populated
First Meaningful Paint 2.9 s
First Meaningful Paint measures when the primary content of a page is visible
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
First Contentful Paint 2.9 s
First Contentful Paint marks the time at which the first text or image is painted
First Contentful Paint (3G) 5970 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
Cumulative Layout Shift 0.036
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Total Blocking Time 600 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Minimize third-party usage Third-party code blocked the main thread for 140 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
Reduce JavaScript execution time 2.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Max Potential First Input Delay 570 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task

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
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
Warning! Your website is not SSL secured (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
Congratulations! Your site not 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 05:28:20 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Set-Cookie: __cfduid=d3a5aca0e00c8b63a2acd8928272766091600925300; expires=Sat, 24-Oct-20 05:28:20 GMT; path=/; domain=.smashedpumpkincafe.co.nz; HttpOnly; SameSite=Lax; Secure
Vary: Accept-Encoding
Vary: Accept-Encoding
Last-Modified: Mon, 21 Sep 2020 19:46:33 GMT
Cache-Control: max-age=0
Expires: Thu, 24 Sep 2020 05:28:20 GMT
CF-Cache-Status: DYNAMIC
cf-request-id: 05602e8e440000da462d837200000001
Expect-CT: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
Server: cloudflare
CF-RAY: 5d7a19f6da2eda46-SYD
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records