Salt.Studio - Info salt.studio

salt.studio receives about 272 unique visitors and 272 (1.00 per visitor) page views per day which should earn about $1.11/day from advertising revenue. Estimated site value is $810.65. According to Alexa Traffic Rank salt.studio is ranked number 4,757,443 in the world and 6.0E-6% of global Internet users visit it. Site is hosted in Provo, Utah, 84606, United States and links to network IP address 162.241.216.173. This server supports HTTPS and HTTP/2.

About - salt.studio


Technologies used on Website

SEO
All in One SEO Pack
Web Servers
Apache
Analytics
Google Analytics
JavaScript Frameworks
RequireJS
JavaScript Libraries
Slick
jQuery Migrate
jQuery
CMS
WordPress
Blogs
WordPress
Programming Languages
PHP
Databases
MySQL

salt.studio Profile

Title: Salt.Studio Furniture and Space. Salt Studio Utah
Last update was 134 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with salt.studio in any way. Only publicly available statistics data are displayed.

How popular is salt.studio?

272 daily visitors
Is this your site?
Verify your site's metrics.
Daily Unique Visitors:
272
Monthly Unique Visitors:
6,528
Pages per Visit:
1.00
Daily Pageviews:
272
Alexa Rank:
4,757,443 visit alexa
Alexa Reach:
6.0E-6%   (of global internet users)
Avg. visit duration:
n/a
Bounce rate:
n/a
*All traffic values are estimates only.

Alexa Traffic Ranks
Search Traffic

Visitors by country

Currently Not Available

Where do visitors go on this site?

Currently Not Available

Competitive Data

SEMrush
Domain:
  salt.studio
Rank:
(Rank based on keywords, cost and organic traffic)
  n/a
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  0
Organic Traffic:
(Number of visitors coming from top 20 search results)
  0
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $0.00
Adwords Keywords:
(Keywords a website is buying in Google AdWords for ads that appear in paid search results)
  0
Adwords Traffic:
(Number of visitors brought to the website via paid search results)
  0
Adwords Cost:
(Estimated budget spent for buying keywords in Google AdWords for ads that appear in paid search results - monthly estimation)
  $0.00

+ Moz Data

Domain Authority:
  n/a
Page Authority:
  n/a
MozRank:
  n/a

+ How socially engaged is salt.studio?

Facebook:
  0
Google +:
  0
Linkedin:
  0
Stumbles:
  0
Buffer:
  0
Pins:
  0

+ Ad Experience Report

Summary of the ad experience rating of a site for a specific platform.

Desktop summary

Root domain:
salt.studio
Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed


Mobile summary

Region:
(The Ad Standard region to which this site has been assigned.)
Pending
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

+ Abusive Experience Report

Root domain:
salt.studio
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

+ How much salt.studio can earn?

Daily Revenue:
$1.11
Monthly Revenue:
$33.30
Yearly Revenue:
$405.15
*All earnings values are estimates only.

Daily earning by country

Currently Not Available

How much money do salt.studio lose due to Adblock?

Daily Revenue Loss:
n/a
Monthly Revenue Loss:
n/a
Yearly Revenue Loss:
n/a
Daily Pageviews Blocked:
n/a
Monthly Pageviews Blocked:
n/a
Yearly Pageviews Blocked:
n/a
*All earnings values are estimates only.

Daily revenue loss by country

Currently Not Available

How much is salt.studio worth?

Website Value:
$810.65

+ Where is salt.studio hosted?

Server IP:
162.241.216.173
ASN:
AS46606 
ISP:
Unified Layer 
Server Location:
Provo
Utah, UT
84606
United States, US
 

Other sites hosted on 162.241.216.173

+ How fast does salt.studio load?

Average Load Time:
n/a ms n/a % of sites are slower

Page Speed (Google PageSpeed Insights) - Desktop

96
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Max Potential First Input Delay 20 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 0.8 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
Estimated Input Latency 10 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. Learn more.
Total Blocking Time 0 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.
Speed Index 1.3 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 0.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 0.7 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 0.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.

Screenshot Thumbnails

This is what the load of your site looked like.

Serve static assets with an efficient cache policy - 16 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
0 ms231 KB
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
0 ms42 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
0 ms34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
0 ms34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
0 ms32 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
0 ms14 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
0 ms8 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
0 ms7 KB
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
0 ms5 KB
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
0 ms2 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
0 ms2 KB
http://salt.studio/wp-includes/js/wp-embed.min.js?ver=4.6.16
0 ms1 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
0 ms1 KB
http://salt.studio/wp-content/themes/salt-studio/lib/images/x.png
0 ms1 KB
http://www.google-analytics.com/plugins/ua/linkid.js
3600000 ms1 KB
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB0 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
980 ms
9 ms
991 ms
82 ms
1079 ms
38 ms
1128 ms
11 ms
1167 ms
24 ms
1204 ms
6 ms
1213 ms
15 ms
1228 ms
10 ms
1273 ms
5 ms
1283 ms
6 ms
1431 ms
56 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
56 ms
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
54 ms
Minify CSS - Potential savings of 4 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB4 KB
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. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
138 ms5 ms1 ms
http://salt.studio/
76 ms75 ms1 ms
Avoids enormous network payloads - Total size was 436 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
231 KB
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
42 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB
http://www.google-analytics.com/analytics.js
18 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
14 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
7 KB
http://salt.studio/
5 KB
Minimizes main-thread work - 0.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
161 ms
Rendering
59 ms
Other
44 ms
Style & Layout
19 ms
Script Parsing & Compilation
12 ms
Parse HTML & CSS
12 ms
Serve images in next-gen formats - Potential savings of 40 KB
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. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
231 KB40 KB
Avoids an excessive DOM size - 55 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). Learn more.

Statistic
ElementValue
Total DOM Elements
55
Maximum DOM Depth
7
Maximum Child Elements
12
Minify JavaScript - Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB12 KB
Keep request counts low and transfer sizes small - 18 requests • 436 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
18436 KB
Image
3232 KB
Script
9116 KB
Font
268 KB
Stylesheet
315 KB
Document
15 KB
Media
00 KB
Other
00 KB
Third-party
319 KB
Eliminate render-blocking resources - Potential savings of 490 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
1 KB70
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
7 KB150
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB150
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
42 KB310
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB110
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
14 KB190
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
2 KB70
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB190
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
2 KB70
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://salt.studio/
0 ms943 ms5 KB13 KB200text/htmlDocument
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
957 ms1007 ms1 KB2 KB200text/cssStylesheet
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
957 ms1051 ms7 KB42 KB200text/cssStylesheet
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
958 ms1052 ms8 KB30 KB200text/cssStylesheet
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
958 ms1124 ms42 KB95 KB200application/javascriptScript
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
959 ms1050 ms5 KB10 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
959 ms1086 ms14 KB41 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
959 ms1052 ms2 KB3 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
960 ms1091 ms32 KB90 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
960 ms1055 ms2 KB5 KB200application/javascriptScript
http://salt.studio/wp-includes/js/wp-embed.min.js?ver=4.6.16
960 ms1049 ms1 KB1 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
962 ms967 ms18 KB43 KB200text/javascriptScript
http://www.google-analytics.com/plugins/ua/linkid.js
1051 ms1056 ms1 KB2 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j79&aip=1&a=1002370204&t=pageview&_s=1&dl=http%3A%2F%2Fsalt.studio%2F&ul=en-us&de=UTF-8&dt=Salt.Studio%20Furniture%20and%20Space.%20Salt%20Studio%20Utah&sd=24-bit&sr=800x600&vp=1350x940&je=0&_u=aGBAAAAj~&jid=673577400&gjid=1121532834&cid=982481141.1574501365&tid=UA-83358304-1&_gid=1330188750.1574501365&_r=1&z=966134046
1104 ms1108 ms0 KB0 KB200image/gifImage
http://salt.studio/wp-content/themes/salt-studio/lib/images/x.png
1181 ms1239 ms1 KB0 KB200image/pngImage
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
1182 ms1379 ms231 KB231 KB200image/jpegImage
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
1183 ms1238 ms34 KB34 KB200font/woff2Font
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
1185 ms1240 ms34 KB34 KB200font/woff2Font
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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

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. Learn more.

Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Avoid chaining critical requests - 12 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
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. Learn more.

Reduce server response times (TTFB) - Root document took 940 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.


Page Speed (Google PageSpeed Insights) - Mobile

92
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Origin Data

All pages served from this origin have an speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Lab Data

Speed Index 3.5 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more.
First CPU Idle 2.8 s
First CPU Idle marks the first time at which the page's main thread is quiet enough to handle input. Learn more.
First Contentful Paint 2.3 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more.
Performance budget
Keep the quantity and size of network requests under the targets set by the provided performance budget. Learn more.
First Meaningful Paint 2.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more.
Max Potential First Input Delay 60 ms
The maximum potential First Input Delay that your users could experience is the duration, in milliseconds, of the longest task. Learn more.
Time to Interactive 2.9 s
Time to interactive is the amount of time it takes for the page to become fully interactive. Learn more.
First Contentful Paint (3G) 4746.5 ms
First Contentful Paint 3G marks the time at which the first text or image is painted while on a 3G network. Learn more.
Estimated Input Latency 10 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. Learn more.
Total Blocking Time 20 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds.

Screenshot Thumbnails

This is what the load of your site looked like.

Avoids enormous network payloads - Total size was 436 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.

URL
Size
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
231 KB
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
42 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB
http://www.google-analytics.com/analytics.js
18 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
14 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
7 KB
http://salt.studio/
5 KB
Minimizes main-thread work - 1.3 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Category
Time Spent
Script Evaluation
579 ms
Rendering
333 ms
Other
175 ms
Style & Layout
78 ms
Parse HTML & CSS
50 ms
Script Parsing & Compilation
46 ms
Garbage Collection
2 ms
Serve images in next-gen formats - Potential savings of 40 KB
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. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
231 KB40 KB
Avoids an excessive DOM size - 55 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). Learn more.

Statistic
ElementValue
Total DOM Elements
55
Maximum DOM Depth
7
Maximum Child Elements
12
Minify JavaScript - Potential savings of 12 KB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB12 KB
Keep request counts low and transfer sizes small - 17 requests • 436 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Resource Type
RequestsTransfer Size
Total
17436 KB
Image
2231 KB
Script
9116 KB
Font
268 KB
Stylesheet
315 KB
Document
15 KB
Media
00 KB
Other
00 KB
Third-party
319 KB
Eliminate render-blocking resources - Potential savings of 1,590 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
1 KB180
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
7 KB480
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB480
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
42 KB1080
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
5 KB480
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
14 KB780
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
2 KB180
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
32 KB630
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
2 KB180
Network Requests
Lists the network requests that were made during page load.

URL
Start TimeEnd TimeTransfer SizeResource SizeStatus CodeMIME TypeResource Type
http://salt.studio/
0 ms920 ms5 KB13 KB200text/htmlDocument
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
937 ms1023 ms1 KB2 KB200text/cssStylesheet
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
938 ms1091 ms7 KB42 KB200text/cssStylesheet
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
938 ms1030 ms8 KB30 KB200text/cssStylesheet
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
939 ms1065 ms42 KB95 KB200application/javascriptScript
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
940 ms1028 ms5 KB10 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
940 ms1095 ms14 KB41 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
940 ms1029 ms2 KB3 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
941 ms1093 ms32 KB90 KB200application/javascriptScript
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
941 ms1092 ms2 KB5 KB200application/javascriptScript
http://salt.studio/wp-includes/js/wp-embed.min.js?ver=4.6.16
941 ms1027 ms1 KB1 KB200application/javascriptScript
http://www.google-analytics.com/analytics.js
943 ms948 ms18 KB43 KB200text/javascriptScript
http://www.google-analytics.com/plugins/ua/linkid.js
1033 ms1038 ms1 KB2 KB200text/javascriptScript
http://www.google-analytics.com/r/collect?v=1&_v=j79&aip=1&a=780224915&t=pageview&_s=1&dl=http%3A%2F%2Fsalt.studio%2F&ul=en-us&de=UTF-8&dt=Salt.Studio%20Furniture%20and%20Space.%20Salt%20Studio%20Utah&sd=24-bit&sr=412x660&vp=412x660&je=0&_u=aGBAAAAj~&jid=31427347&gjid=297376126&cid=1258552272.1574501357&tid=UA-83358304-1&_gid=744577882.1574501357&_r=1&z=1932656104
1061 ms1066 ms0 KB0 KB200image/gifImage
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
1145 ms1339 ms231 KB231 KB200image/jpegImage
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
1145 ms1229 ms34 KB34 KB200font/woff2Font
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
1145 ms1194 ms34 KB34 KB200font/woff2Font
Serve static assets with an efficient cache policy - 15 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.

URL
Cache TTLSize
http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg
0 ms231 KB
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
0 ms42 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
0 ms34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
0 ms34 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
0 ms32 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
0 ms14 KB
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
0 ms8 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
0 ms7 KB
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
0 ms5 KB
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
0 ms2 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
0 ms2 KB
http://salt.studio/wp-includes/js/wp-embed.min.js?ver=4.6.16
0 ms1 KB
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
0 ms1 KB
http://www.google-analytics.com/plugins/ua/linkid.js
3600000 ms1 KB
http://www.google-analytics.com/analytics.js
7200000 ms18 KB
Minimize third-party usage - Third-party code blocked the main thread for 20 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. Learn more.

Third-Party
SizeMain-Thread Blocking Time
19 KB22 ms
Tasks
Lists the toplevel main thread tasks that executed during page load.

Start Time
End Time
943 ms
11 ms
957 ms
83 ms
1046 ms
20 ms
1071 ms
11 ms
1115 ms
26 ms
1155 ms
5 ms
1162 ms
13 ms
1176 ms
9 ms
1215 ms
6 ms
1254 ms
6 ms
1369 ms
80 ms
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

URL
Potential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Medium.woff2
84 ms
http://salt.studio/wp-content/themes/salt-studio/lib/css/fonts/Unica77LLWeb-Regular.woff2
48 ms
Minify CSS - Potential savings of 4 KB
Minifying CSS files can reduce network payload sizes. Learn more.

URL
SizePotential Savings
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16
8 KB4 KB
JavaScript execution time - 0.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

URL
Total CPU TimeScript EvaluationScript Parse
Other
653 ms16 ms5 ms
http://salt.studio/
303 ms298 ms5 ms
http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
134 ms120 ms8 ms
http://www.google-analytics.com/analytics.js
80 ms73 ms6 ms
Defer offscreen images
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.

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. Learn more.

Properly size images
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS
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. Learn more.

Avoid chaining critical requests - 12 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. Learn more.

Preload key requests
Consider using `` to prioritize fetching resources that are currently requested later in page load. Learn more.

Avoid multiple page redirects
Redirects introduce additional delays before the page can be loaded. Learn more.

User Timing marks and measures
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Use video formats for animated content
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. Learn more.

Reduce server response times (TTFB) - Root document took 920 ms
Time To First Byte identifies the time at which your server sends a response. Learn more.

Efficiently encode images
Optimized images load faster and consume less cellular data. Learn more.

Enable text compression
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

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. Learn more.

Preconnect to required origins
Consider adding `preconnect` or `dns-prefetch` resource hints to establish early connections to important third-party origins. Learn more.

Page Speed (Google PageSpeed Insights) - v2

Suggestions Summary

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 6 blocking script resources and 3 blocking CSS resources. This causes a delay in rendering your page.

None of the above-the-fold content on your page could be rendered without waiting for the following resources to load. Try to defer or asynchronously load blocking resources, or inline the critical portions of those resources directly in the HTML.Remove render-blocking JavaScript:

http://salt.studio/wp-includes/js/jquery/jquery.js?ver=1.12.4
http://salt.studio/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.4.1
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.min.js?ver=4.6.16
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/jquery-mousewheel/jquery.mousewheel.min.js?ver=4.6.16
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16
http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16
Optimize CSS Delivery of the following:

http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/slick-carousel/slick/slick.css?ver=4.6.16
http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.min.css?ver=4.6.16
http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16

Reduce server response time

In our test, your server responded in 0.67 seconds.

There are many factors that can slow down your server response time. Please read our recommendations to learn how you can monitor and measure where your server is spending the most time.

Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://salt.studio/wp-content/uploads/2016/06/TEKNION-Navigate_Gable_Bevel_Leg_upstage_web.jpg (expiration not specified)
http://www.google-***ytics.com/plugins/ua/linkid.js (60 minutes)
http://www.google-***ytics.com/***ytics.js (2 hours)

Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and *** time.

Minify JavaScript for the following resources to reduce their size by 8.8KiB (39% reduction).

Minifying http://salt.studio/wp-content/themes/salt-studio/lib/bower_components/malihu-custom-scrollbar-plugin/jquery.mCustomScrollbar.js?ver=4.6.16 could save 8.6KiB (40% reduction) after compression.
Minifying http://salt.studio/wp-content/themes/salt-studio/lib/js/scripts.js?ver=4.6.16 could save 177B (13% reduction) after compression.

Minify CSS

Compacting CSS code can save many bytes of data and speed up download and p*** times.

Minify CSS for the following resources to reduce their size by 2.4KiB (41% reduction).

Minifying http://salt.studio/wp-content/themes/salt-studio/lib/css/style.css?ver=4.6.16 could save 2.4KiB (41% reduction) after compression.

Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and p*** times.

Minify HTML for the following resources to reduce their size by 450B (11% reduction).

Minifying http://salt.studio/ could save 450B (11% reduction) after compression.
Avoid landing page redirects
Your page has no redirects. Learn more about avoiding landing page redirects.
Avoid plugins
Your page does not appear to use plugins, which would prevent content from being usable on many platforms. Learn more about the importance of avoiding plugins.
Configure the viewport
Your page specifies a viewport matching the device's size, which allows it to render properly on all devices. Learn more about configuring viewports.
Enable compression
You have compression enabled. Learn more about enabling compression.
Optimize images
Your images are optimized. Learn more about optimizing images.
Prioritize visible content
You have the above-the-fold content properly prioritized. Learn more about prioritizing visible content.
Size content to viewport
The contents of your page fit within the viewport. Learn more about sizing content to the viewport.
Size tap targets appropriately
All of your page's links/buttons are large enough for a user to easily tap on a touchscreen. Learn more about sizing tap targets appropriately.
Use legible font sizes
The text on your page is legible. Learn more about using legible font sizes.
Download optimized image, JavaScript, and CSS resources for this page.

+ Does salt.studio use compression?

salt.studio use gzip compression.
Original size: 13.42 KB
Compressed size: 4.84 KB
File reduced by: 8.58 KB (63%)

+ Google Safe Browsing

This site is not currently listed as suspicious

MyWot.com Reputation Ratings

Trustworthiness:
  n/a
Vendor reliability:
  n/a
Privacy:
  n/a
Child safety:
  n/a

+ SSL Checker - SSL Certificate Verify

salt.studio supports HTTPS
loader
Verifying SSL Support. Please wait...
Common Name: salt.studio
Organization:
Location:
Issuer: Let's Encrypt Authority X3
Valid from: Nov 7 16:47:49 2019 GMT
Valid until: Feb 5 16:47:49 2020 GMT
Authority:
Keysize:

+ Verify HTTP/2 Support

salt.studio supports HTTP/2
loader
Verifying HTTP/2.0 Support. Please wait...

+ Site Categories (dmoz)

Currently Not Available

+ Http Header

Upgrade: h2c
Connection: Upgrade

HTTP/2 200 
date: Thu, 01 Jan 1970 00:00:00 GMT
server: Apache
link: <http://salt.studio/wp-json/>; rel="https://api.w.org/", <http://salt.studio/>; rel=shortlink
vary: Accept-Encoding
content-encoding: gzip
content-length: 4954
content-type: text/html; charset=UTF-8

+ DNS Lookup

Type Ip Target TTL
HINFO 3600
A 162.241.216.173 3573
NS ns2.bluehost.com 3573
NS ns1.bluehost.com 3573

+ Whois Lookup

Domain Created:
0000-00-00
Domain Age:
 
WhoIs:
 

whois lookup at whois.rightside.co...
\Error - could not open a connection to whois.rightside.co
Last update was 134 days ago
loader
This can take up to 60 seconds. Please wait...

*HypeStat.com is not linking to, promoting or affiliated with salt.studio in any way. Only publicly available statistics data are displayed.

Recently Analyzed Sites

idateexpo.com
13 secs
tur43.es
1 min
idatedownunder.com
1 min
newsr24.com
1 min
aeronet.cz
2 mins
samsonmedia.net
3 mins
idafrosk.com
3 mins
signal.jsxpro.com
3 mins
mymoviebazar.com
4 mins
icul.org
4 mins
WHAT WE RECOMMEND:
We are using the world's No. 1 Marketing Tool to grow our website. Activate your FREE trial today!

BrowserExtension

Install HypeStat extension in your browser to see statistics and technologies used with one click.

Hide/Remove your site data

• Use Show/Hide ESTIMATED data form to hide (Website worth, Daily ads revenue, Daily Visits, Daily Pageviews)
• Use Show/Hide WHOIS data form to hide whois data
• Use Remove form to remove all data
• If you have any problem with REMOVE/HIDE your data just drop an email at support (at) hypestat.com and we will remove/hide your site data manualy.
Make custom Widget for your website
Get the code now!
salt.studio widget