2.7 sec in total
120 ms
1.6 sec
1 sec
Visit foggy-notion.com now to see the best up-to-date Foggy Notion content for United States and also check out these interesting facts you probably never knew about foggy-notion.com
Visit foggy-notion.comWe analyzed Foggy-notion.com page load time and found that the first response time was 120 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
foggy-notion.com performance score
name
value
score
weighting
Value7.9 s
0/100
10%
Value17.9 s
0/100
25%
Value13.4 s
2/100
10%
Value3,470 ms
2/100
30%
Value0.381
27/100
15%
Value19.8 s
2/100
10%
120 ms
9 ms
416 ms
75 ms
98 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Foggy-notion.com, 34% (21 requests) were made to Foggynotionsf.files.wordpress.com and 13% (8 requests) were made to S1.wp.com. The less responsive or slowest element that took the longest time to load (867 ms) relates to the external source Foggynotionsf.files.wordpress.com.
Page size can be reduced by 416.6 kB (17%)
2.5 MB
2.0 MB
In fact, the total size of Foggy-notion.com main page is 2.5 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 60% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.
Potential reduce by 30 B
HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 30 B or 21% of the original size.
Potential reduce by 12.4 kB
Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Foggy Notion images are well optimized though.
Potential reduce by 373.0 kB
It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 373.0 kB or 76% of the original size.
Potential reduce by 31.2 kB
CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Foggy-notion.com needs all CSS files to be minified and compressed as it can save up to 31.2 kB or 79% of the original size.
Number of requests can be reduced by 20 (37%)
54
34
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Foggy Notion. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
foggy-notion.com
120 ms
foggynotionsf.wordpress.com
9 ms
foggynotionsf.wordpress.com
416 ms
75 ms
css
98 ms
87 ms
global.css
80 ms
89 ms
gprofiles.js
188 ms
wpgroho.js
84 ms
jetpack-carousel.css
86 ms
78 ms
80 ms
widgets.js
211 ms
79 ms
725X1342.skimlinks.js
140 ms
w.js
83 ms
merriweather.css
18 ms
global-print.css
1 ms
foggy_logo_horiz_header.jpg
176 ms
sdk.js
152 ms
img_0582.jpg
323 ms
biocalendulavicky-2.jpg
185 ms
clementime2015.jpg
228 ms
urbanairhv.png
464 ms
img_6470.jpg
532 ms
fn_img_1195_theshop.jpg
486 ms
fn_img_1177_pf.jpg
477 ms
fn_img_1187_shrub.jpg
552 ms
fn_img_1189_cait.jpg
614 ms
megshimekxl.jpg
677 ms
cdmustard.jpg
736 ms
seccerorange.jpg
757 ms
daren2tone.jpg
812 ms
hendleyhardgoods_header_2.png
554 ms
gwenhendleyhoriz.jpg
681 ms
hendley_board1.jpg
718 ms
hendley_boards2.jpg
809 ms
banner.jpg
777 ms
keykite-logo.gif
721 ms
keykitegems.jpg
867 ms
AWM5wXtMJeRP-AcRTgT4qQ.ttf
161 ms
107 ms
hovercard.css
87 ms
services.css
121 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
73 ms
70 ms
Noticons.svg
35 ms
BaABdRAi2AAAA
21 ms
merriweather-bold-webfont.ttf
33 ms
merriweather-regular-webfont.ttf
53 ms
merriweather-light-webfont.ttf
54 ms
g.gif
64 ms
g.gif
46 ms
g.gif
48 ms
176 ms
xd_arbiter.php
43 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
41 ms
jot
91 ms
link
27 ms
track.php
66 ms
foggy-notion.com accessibility score
Names and labels
These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Buttons do not have an accessible name
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
foggy-notion.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
foggy-notion.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).
Impact
Issue
Document uses legible font sizes
N/A
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Foggy-notion.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Foggy-notion.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
foggy-notion.com
Open Graph description is not detected on the main page of Foggy Notion. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: