3.8 sec in total
143 ms
3.1 sec
560 ms
Welcome to mysql.com homepage info - get ready to check MySQL best content for China right away, or after learning these important things about mysql.com
Visit mysql.comWe analyzed Mysql.com page load time and found that the first response time was 143 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
mysql.com performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value6.3 s
10/100
25%
Value6.4 s
40/100
10%
Value2,560 ms
4/100
30%
Value0.009
100/100
15%
Value14.7 s
8/100
10%
143 ms
246 ms
1074 ms
172 ms
356 ms
Our browser made a total of 45 requests to load all elements on the main page. We found that 7% of them (3 requests) were addressed to the original Mysql.com, 58% (26 requests) were made to Labs.mysql.com and 9% (4 requests) were made to Oracle.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Mysql.com.
Page size can be reduced by 65.8 kB (15%)
452.1 kB
386.2 kB
In fact, the total size of Mysql.com main page is 452.1 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. 55% of websites need less resources to load. Images take 288.7 kB which makes up the majority of the site volume.
Potential reduce by 33.1 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. This page needs HTML code to be minified as it can gain 8.1 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 33.1 kB or 81% of the original size.
Potential reduce by 77 B
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. MySQL images are well optimized though.
Potential reduce by 29.7 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 29.7 kB or 31% of the original size.
Potential reduce by 3.0 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. Mysql.com needs all CSS files to be minified and compressed as it can save up to 3.0 kB or 11% of the original size.
Number of requests can be reduced by 12 (39%)
31
19
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of MySQL. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
mysql.com
143 ms
mysql.com
246 ms
www.mysql.com
1074 ms
main-20230830.min.css
172 ms
page-20230830.min.css
356 ms
notice
151 ms
truste-oraclelib.js
83 ms
site-20231211.min.js
318 ms
oracle-chat.js
104 ms
log
105 ms
v1.7-4543
23 ms
E6BB6-B37B4-898B7-F97BA-BBCDB
428 ms
mysql-logo.svg
427 ms
b1280-grey-gradient-background.jpg
427 ms
b1280-mysql-mds-aws-azure6.en.jpg
496 ms
b1280-blue-gradient-background.jpg
415 ms
site-sprite1.png
425 ms
op-sprite1.png
559 ms
list-disc-orange.png
559 ms
logo-sprite-x2-v3.jpg
655 ms
oracle-logo-new.svg
643 ms
get
300 ms
ora_mysql.js
196 ms
odc.js
82 ms
opensans-regular-webfont.woff
349 ms
opensans-semibold-webfont.woff
606 ms
opensans-light-webfont.woff
360 ms
opensans-bold-webfont.woff
349 ms
opensans-extrabold-webfont.woff
493 ms
opensans-italic-webfont.woff
505 ms
opensans-semibolditalic-webfont.woff
503 ms
opensans-lightitalic-webfont.woff
509 ms
opensans-bolditalic-webfont.woff
509 ms
opensans-extrabolditalic-webfont.woff
509 ms
icons4.woff
603 ms
config.json
42 ms
ora_code.js
145 ms
analytics-production.js
114 ms
b1280-mysql-ee-generic2.en.jpg
135 ms
s31709450797643
22 ms
common.js
67 ms
analytics.js
60 ms
print-20230830.min.css
110 ms
id
54 ms
infinity_common.js
63 ms
mysql.com accessibility score
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
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
mysql.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
mysql.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mysql.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Mysql.com 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.
mysql.com
Open Graph description is not detected on the main page of MySQL. 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: