Your Website Score is

Similar Ranking

14
PROTECTIVE HOMOEOPATHY
protectivehomoeopathy.blogspot.com
14
HOME | AVA AUGUST
avaaugust.com
14
ZEBIQ TECHNOLOGY - ZEBIQ TECHNOLOGY
zebiqtechnology.com
14
BEATS & SMILES
midlandsdj.com
14
SECURITY VERIFICATION
uniqueradio.org
14
ANMOL- INTERIOR
aidkol.blogspot.com

Latest Sites

19
SENILE TEAM DEV LOG
senileteam.com
14
BOXHERO.IN
boxhero.in
21
HUYCHESS
huychess.sbs
96
YOUTUBE
youtu.be
9
YOUTUBE
youtube.com
19
YUPPOW - FREE HD MOVIES AND TV SHOWS STREAMING ONLINE
yuppow.org

Top Technologies

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

14 hollandsehoogtes.nl Last Updated: 1 year

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

Desktop

Mobile

Performance Desktop Score 81%
Best Practices Desktop Score 100%
SEO Desktop Score 100%
Performance Mobile Score 62%
Best Practices Mobile Score 100%
SEO Mobile Score 100%
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 26 Characters
WELKOM - HOLLANDSE HOOGTES
Meta Description 338 Characters
Hollandse Hoogtes is teler in het Experiment Gesloten Coffeeshopketen. Met ruim 40 jaar ervaring in de Vaderlandse cannabis- en coffeeshopcultuur zijn we geen groentje. Onze producten zijn van de hoogste kwaliteit. Ze worden uit de beste genetica gekweekt onder absoluut perfecte omstandigheden. Beter dan wat ooit in Nederland is gedaan.
Effective URL 27 Characters
https://hollandsehoogtes.nl
Excerpt Page content
Welkom - Hollandse Hoogtes Ga naar de inhoud ...
Keywords Cloud Density
voor21 wiet18 hoogtes15 hollandse15 stuk13 legale13 zijn12 onze10 reis8 coffeeshops7
Keyword Consistency Keyword density is one of the main terms in SEO
Keyword Freq Title Desc Domain H1 H2
voor 21
wiet 18
hoogtes 15
hollandse 15
stuk 13
legale 13
zijn 12
onze 10
reis 8
coffeeshops 7
Google Preview Your look like this in google search result
WELKOM - HOLLANDSE HOOGTES
https://hollandsehoogtes.nl
Hollandse Hoogtes is teler in het Experiment Gesloten Coffeeshopketen. Met ruim 40 jaar ervaring in de Vaderlandse cannabis- en coffeeshopcultuur zijn
Robots.txt File Detected
Sitemap.xml File Detected
Page Size Code & Text Ratio
Document Size: ~261.3 KB
Code Size: ~121.28 KB
Text Size: ~140.03 KB Ratio: 53.59%

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
JavaScript execution time 0.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
Minimizes main-thread work 1.1 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Avoid chaining critical requests 34 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 Meaningful Paint 0.7 s
First Meaningful Paint measures when the primary content of a page is visible
Serve static assets with an efficient cache policy 60 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
Reduce unused CSS Potential savings of 46 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity
Speed Index 3.4 s
Speed Index shows how quickly the contents of a page are visibly populated
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.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
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 1 long task 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
Avoid enormous network payloads Total size was 8,537 KiB
Large network payloads cost users real money and are highly correlated with long load times
Max Potential First Input Delay 130 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Largest Contentful Paint element 2,100 ms
This is the largest contentful element painted within the viewport
Properly size images Potential savings of 518 KiB
Serve images that are appropriately-sized to save cellular data and improve load time
Avoid large layout shifts 1 layout shift found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to [windowing](https://web.dev/articles/cls#what_is_cls)
Eliminate render-blocking resources Potential savings of 370 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Efficiently encode images Potential savings of 157 KiB
Optimized images load faster and consume less cellular data
Serve images in next-gen formats Potential savings of 5,741 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 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 2,980 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint 2.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Cumulative Layout Shift 0.001
Cumulative Layout Shift measures the movement of visible elements within the viewport
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Avoid an excessive DOM size 1,199 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)
Use video formats for animated content Potential savings of 409 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Total Blocking Time 40 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds

Mobile

Mobile Screenshot
Largest Contentful Paint 8.4 s
Largest Contentful Paint marks the time at which the largest text or image is painted
Avoid serving legacy JavaScript to modern browsers Potential savings of 11 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
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
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
Speed Index 6.0 s
Speed Index shows how quickly the contents of a page are visibly populated
Time to Interactive 6.6 s
Time to Interactive is the amount of time it takes for the page to become fully interactive
First Contentful Paint 2.7 s
First Contentful Paint marks the time at which the first text or image is painted
Reduce initial server response time Root document took 1,730 ms
Keep the server response time for the main document short because all other requests depend on it
Largest Contentful Paint element 8,400 ms
This is the largest contentful element painted within the viewport
Document uses legible font sizes 99.98% 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
Minimize main-thread work 3.5 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this
Total Blocking Time 240 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds
Avoid an excessive DOM size 1,199 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)
Efficiently encode images Potential savings of 157 KiB
Optimized images load faster and consume less cellular data
Avoid chaining critical requests 34 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
Serve images in next-gen formats Potential savings of 3,038 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption
Serve static assets with an efficient cache policy 57 resources found
A long cache lifetime can speed up repeat visits to your page
Avoid long main-thread tasks 11 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay
Max Potential First Input Delay 310 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task
Use video formats for animated content Potential savings of 409 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes
Avoid non-composited animations 3 animated elements found
Animations which are not composited can be janky and increase CLS
Reduce unused CSS Potential savings of 44 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease 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.7 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this
First Meaningful Paint 2.7 s
First Meaningful Paint measures when the primary content of a page is visible
Avoid enormous network payloads Total size was 5,614 KiB
Large network payloads cost users real money and are highly correlated with long load times
Eliminate render-blocking resources Potential savings of 1,380 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles
Properly size images Potential savings of 54 KiB
Serve images that are appropriately-sized to save cellular data and improve load time

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
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
Warning! You have broken links View links

Alexa Rank

99,999,999

Global Rank

99,999,999

-
Traffic
Search

Domain Available

Domain (TDL) and Typo Status
hollandsehoogtes.co Available
hollandsehoogtes.us Available
hollandsehoogtes.com Available
hollandsehoogtes.org Available
hollandsehoogtes.net Available
hllandsehoogtes.nl Available
yollandsehoogtes.nl Available
nollandsehoogtes.nl Available

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/1.26.1
Date: Thu, 18 Jul 2024 09:50:12 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding
X-Powered-By: PHP/8.2.20
Link: ; rel="https://api.w.org/", ; rel="alternate"; title="JSON"; type="application/json", ; rel=shortlink
Content-Encoding: gzip
DNS Records DNS Resource Records associated with a hostname
View DNS Records