Your Website Score is

Similar Ranking

12
شرکت تحقیقاتی،پژوهشی و مهندسی افرا - شرکت تحقیقاتی،پژوهشی،مهندسی افرا
sadr-afratech.com
12
SALARISADMINISTRATIE EN PERSONEELSADVIES | VAN DEELEN SALARISADMINISTRATIE
vandeelensalaris.nl
12
SWINGIN' MONTPELLIER - SWING AND GYPSY JAZZ BANDS IN MONTPELLIER
swinginmontpellier.com
12
SWEET SHOP | HALAL CANDY KINGS
halalcandykings.co.uk
12
BRANDA, KIŞ BAHÇESI, TENTE, WINTENT, DIJITAL BASKI | İMK BRANDA REKLAM
imkbrandareklam.com
12
YAHITES MINISTRIES – TRUTH | FAMILY | UNITY | PEACE | LOVE
yahites.org
12
THEFILESLOCKER - FILES UPLOAD AND SHARE FOR FREE
thefileslocker.com

Latest Sites

43
PLEASE WAIT... | CLOUDFLARE
voz.vn
23
TRUST CHRIST OR GO TO HELL! - REBUKING THE PUKE. DESTROYING THE WICKED. IN JESUS' NAME.
trustchristorgotohell.org
99
YOUTUBE
youtube.com
96
YOUTUBE
youtu.be
22
HOME | SOIMBIOSIS: CRYPTO RISING
soimbiosis.com
99
YOUTUBE
m.youtube.com
19
F.A.C.E. THE AGENCY: TRAINING & BUSINESS DEVELOPMENT FIRM
face-theagency.com

Top Technologies

Google Font API
Font Scripts
CloudFlare
CDN
Nginx
Web Servers
Apache
Web Servers
WordPress
CMS
Font Awesome
Font Scripts
Twitter Bootstrap
Web Frameworks
Google Tag Manager
Tag Managers

12 halalcandykings.co.uk Last Updated: 3 years

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

Desktop

Mobile

Performance Desktop Score 62%
Best Practices Desktop Score 73%
SEO Desktop Score 100%
Progressive Web App Desktop Score 27%
Performance Mobile Score 28%
Best Practices Mobile Score 73%
SEO Mobile Score 99%
Progressive Web App Mobile Score 25%
Page Authority Authority 1%
Domain Authority Domain Authority 1%
Moz Rank 0.1/10
Bounce Rate Rate 0%
charset Encoding
Great, language/character encoding is specified: UTF-8
Title Tag 30 Characters
SWEET SHOP | HALAL CANDY KINGS
Meta Description 55 Characters
Halal Candy Kings. We are a sweet/cake selling business
Effective URL 32 Characters
http://www.halalcandykings.co.uk
Excerpt Page content
Sweet shop | Halal Candy Kings  This site was designed with the .com website builder. Create your website today.Start NowHomeShopOrdersProductsContactAboutMore0Welcom...
Meta Keywords 2 Detected
Keywords Cloud Density
view8 quick8 price8 product6 halal5 kings5 candy5 proudly2 website2 cake2
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
view 8
quick 8
price 8
product 6
halal 5
kings 5
candy 5
proudly 2
website 2
cake 2
Google Preview Your look like this in google search result
SWEET SHOP | HALAL CANDY KINGS
http://www.halalcandykings.co.uk
Halal Candy Kings. We are a sweet/cake selling business
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~747.79 KB
Code Size: ~269.98 KB
Text Size: ~477.81 KB Ratio: 63.90%

Social Data

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

Desktop

Desktop Screenshot
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
Reduce the impact of third-party code Third-party code blocked the main thread for 600 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
Avoid serving legacy JavaScript to modern browsers Potential savings of 3 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
Does not use HTTPS 25 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 served over 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
Total Blocking Time 510 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
First Contentful Paint 0.8 s
First Contentful Paint marks the time at which the first text or image is painted
Serve static assets with an efficient cache policy 89 resources found
A long cache lifetime can speed up repeat visits to your page
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible
Remove unused JavaScript Potential savings of 162 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Reduce JavaScript execution time 1.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimize main-thread work 3.3 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 520 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)
Time to Interactive 3.3 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 17 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
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
Avoid large layout shifts 5 elements found
These DOM elements contribute most to the CLS of the page.
Includes front-end JavaScript libraries with known security vulnerabilities 5 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 55 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Max Potential First Input Delay 340 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Keep request counts low and transfer sizes small 137 requests • 1,831 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Cumulative Layout Shift 0.002
Cumulative Layout Shift measures the movement of visible elements within the viewport
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Reduce initial server response time Root document took 1,450 ms
Keep the server response time for the main document short because all other requests depend on it
Remove duplicate modules in JavaScript bundles Potential savings of 26 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Remove unused CSS Potential savings of 104 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
Estimated Input Latency 60 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
Speed Index 2.1 s
Speed Index shows how quickly the contents of a page are visibly populated
Minify JavaScript Potential savings of 28 KiB
Minifying JavaScript files can reduce payload sizes and script parse time
First CPU Idle 3.1 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/).
Preload Largest Contentful Paint image Potential savings of 240 ms
Preload the image used by the LCP element in order to improve your LCP time
User Timing marks and measures 158 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
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
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 enormous network payloads Total size was 1,831 KiB
Large network payloads cost users real money and are highly correlated with long load times

Mobile

Mobile Screenshot
Remove duplicate modules in JavaScript bundles Potential savings of 26 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Includes front-end JavaScript libraries with known security vulnerabilities 5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers
First Contentful Paint (3G) 6960 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network
User Timing marks and measures 156 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences
Avoid large layout shifts 2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks 14 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Largest Contentful Paint 8.2 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Speed Index 7.1 s
Speed Index shows how quickly the contents of a page are visibly populated
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
Web app manifest or service worker do not meet the installability requirements 1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement
Preload Largest Contentful Paint image Potential savings of 150 ms
Preload the image used by the LCP element in order to improve your LCP time
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Reduce JavaScript execution time 3.7 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 17 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
Largest Contentful Paint element 1 element found
This is the largest contentful element painted within the viewport
Minimize main-thread work 6.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Reduce the impact of third-party code Third-party code blocked the main thread for 1,770 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
Keep request counts low and transfer sizes small 111 requests • 1,622 KiB
To set budgets for the quantity and size of page resources, add a budget.json file
Avoids enormous network payloads Total size was 1,622 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 890 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Avoids an excessive DOM size 406 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)
Serve static assets with an efficient cache policy 71 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
First CPU Idle 11.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/).
Remove unused JavaScript Potential savings of 86 KiB
Remove unused JavaScript to reduce bytes consumed by network activity
Remove unused CSS Potential savings of 88 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
Does not use HTTPS 25 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 served over 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
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
Avoid serving legacy JavaScript to modern browsers Potential savings of 3 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
Reduce initial server response time Root document took 1,420 ms
Keep the server response time for the main document short because all other requests depend on it
Tap targets are not sized appropriately 92% 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
Time to Interactive 12.5 s
Time to interactive is the amount of time it takes for the page to become fully interactive
First Meaningful Paint 3.2 s
First Meaningful Paint measures when the primary content of a page is visible
First Contentful Paint 3.2 s
First Contentful Paint marks the time at which the first text or image is painted
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
Total Blocking Time 1,020 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Estimated Input Latency 330 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

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
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

Domain Available

Domain (TDL) and Typo Status
halalcandykings.co.co Available
halalcandykings.co.us Available
halalcandykings.co.com Already Registered
halalcandykings.co.org Already Registered
halalcandykings.co.net Available
hlalcandykings.co.uk Available
yalalcandykings.co.uk Available
nalalcandykings.co.uk Available

Information Server

Response Header HTTP headers carry information about the client browser, the requested page and the server
HTTP/1.1 200 OK
Date: Sun, 25 Apr 2021 21:29:33 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
link: ; rel=preconnect; crossorigin;,; rel=preconnect;,; rel=preconnect; crossorigin;,; rel=preconnect; crossorigin;,; rel=preconnect;,; rel=preconnect; crossorigin;,
etag: W/"fe8cd7b2358c3bb08e00fcaff236cc8f"
content-language: en
Age: 2
Set-Cookie: ssr-caching="cache#desc=hit#varnish=hit#dc#desc=nane1";Version=1;Expires=Sun, 25-Apr-2021 21:29:51 GMT;Max-Age=20
Server-Timing: cache;desc=hit, varnish;desc=hit, dc;desc=nane1
X-Seen-By: sHU62EDOGnH2FBkJkG/Wx8EeXWsWdHrhlvbxtlynkViHxL9sg6uVY+ot0VYPU+Fv,qquldgcFrj2n046g4RNSVBXNYRPnTS+SHXsljeObQkY=,2d58ifebGbosy5xc+FRalnsiONBF87yiERgii8F4nlNjlwACyyCym+yn1mzZPzzIYMlPRo5llZAtxbV7yiXIgWATpQpNjnhpH1r6ososkiQ=,2UNV7KOq4oGjA5+PKsX47J3GUfYUU4ZAjIW0JalAV84=
Cache-Control: no-cache
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Vary: Accept-Encoding
X-Wix-Request-Id: 1619386173.691340873879126723
X-Content-Type-Options: nosniff
Content-Encoding: gzip
Server: Pepyaka/1.19.0
DNS Records DNS Resource Records associated with a hostname
View DNS Records