2.3 sec in total
401 ms
1.8 sec
123 ms
Click here to check amazing Mocky content for Turkey. Otherwise, check out these important facts you probably never knew about mocky.io
Don't wait for the backend to be ready, generate custom API responses with Mocky and start working on your application straightaway
Visit mocky.ioWe analyzed Mocky.io page load time and found that the first response time was 401 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
mocky.io performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value14.3 s
0/100
25%
Value10.5 s
7/100
10%
Value540 ms
55/100
30%
Value0.288
42/100
15%
Value14.1 s
9/100
10%
401 ms
186 ms
384 ms
390 ms
410 ms
Our browser made a total of 29 requests to load all elements on the main page. We found that 66% of them (19 requests) were addressed to the original Mocky.io, 10% (3 requests) were made to Platform.twitter.com and 10% (3 requests) were made to Widget.uservoice.com. The less responsive or slowest element that took the longest time to load (820 ms) belongs to the original domain Mocky.io.
Page size can be reduced by 39.2 kB (51%)
76.9 kB
37.7 kB
In fact, the total size of Mocky.io main page is 76.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. HTML takes 48.1 kB which makes up the majority of the site volume.
Potential reduce by 35.7 kB
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 35.7 kB or 74% of the original size.
Potential reduce by 3.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. Obviously, Mocky needs image optimization as it can save up to 3.4 kB or 30% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 34 B
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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 19 (70%)
27
8
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mocky. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and as a result speed up the page load time.
mocky.io
401 ms
www.mocky.io
186 ms
main.css
384 ms
jquery-1.9.1.min.js
390 ms
select2.js
410 ms
lodash-1.2.1.min.js
249 ms
i18n.js
168 ms
http.js
181 ms
main.js
335 ms
ace.js
820 ms
uservoices.js
343 ms
fr.png
86 ms
us.png
90 ms
pt-br.png
86 ms
octocat.png
80 ms
widgets.js
136 ms
ga.js
5 ms
__utm.gif
23 ms
nIFm1w8BswV6OuuCXMdbAw.js
76 ms
theme-tomorrow.js
87 ms
mode-json.js
89 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
27 ms
select2.png
116 ms
tweet_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
71 ms
feedback-tab.png
7 ms
tab-horizontal-dark-3efc2033e3bb06b1eefaa3431d3d47d8.png
4 ms
worker-json.js
168 ms
track.js
164 ms
jot
81 ms
mocky.io 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
mocky.io 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
mocky.io SEO score
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mocky.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Mocky.io main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.
mocky.io
Open Graph description is not detected on the main page of Mocky. 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: