2.9 sec in total
714 ms
835 ms
1.4 sec
Visit autopic.net now to see the best up-to-date Autopic content and also check out these interesting facts you probably never knew about autopic.net
斜视的人是不是脑子有些问题
Visit autopic.netWe analyzed Autopic.net page load time and found that the first response time was 714 ms and then it took 2.2 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.
autopic.net performance score
name
value
score
weighting
Value1.2 s
99/100
10%
Value1.2 s
100/100
25%
Value1.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value1.2 s
100/100
10%
714 ms
25 ms
24 ms
25 ms
25 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Autopic.net, 98% (55 requests) were made to Dljyedu.com. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Autopic.net.
Page size can be reduced by 29.6 kB (73%)
40.8 kB
11.2 kB
In fact, the total size of Autopic.net main page is 40.8 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 40.8 kB which makes up the majority of the site volume.
Potential reduce by 29.6 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 29.6 kB or 73% of the original size.
We found no issues to fix!
0
0
Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.
autopic.net
714 ms
bootstrap-3.1.1.min.css
25 ms
style.css
24 ms
googleapis.css
25 ms
swiper.min.css
25 ms
font-awesome.css
25 ms
chocolat.css
26 ms
logo.png
25 ms
f46fc3a33f1c0c4b1b88a099faa045ab.jpg
25 ms
02f13e3214d1b1217de0d881f1ec72a3.jpg
24 ms
f4e0082403d739de547a9fd192204a67.jpg
25 ms
50c01a5627f97bed584287d7c6149179.jpg
25 ms
886502fef7cbefecfea7e304dbec8539.jpg
26 ms
6a57d111e058a45334c0472562765d21.jpg
26 ms
f6616fae4e184b3287de2a3f13e6eaac.jpg
26 ms
83d89f0dc85cd0649866692295d49a77.png
26 ms
7a7732f01e33782c3d7f8a6ace0a747f.png
26 ms
5151886e58ad022c417f05a275b88660.png
26 ms
785012040d77e72c14885ec527e68b9a.png
26 ms
f69247a2edb2ec3d5a8e750c46324ae6.jpg
26 ms
0429e689fd7d043ee5fbee49e2fde29c.jpg
26 ms
bcd6db01ab6532f94af7fb62780834c3.jpg
26 ms
20883599597c4333a46622011033f921.jpg
26 ms
c74e802cffa0d5d0115b76d4ffe28464.jpg
26 ms
e9f2a1e16ada98b46b105de311143a46.jpg
26 ms
823f23d8043f1e8e1f4bd78353a4daee.jpg
25 ms
d2563c654262b4a5064cfe7498dc6b9f.jpg
25 ms
726f2968c11cece8c532af75fa96ab60.png
22 ms
5bd1ce884f113d11d2eb2561b5844f3b.png
21 ms
59acda7540d5d4dec8ed2713f4121f3b.png
21 ms
37996034d5a397c2b3fa22e415929811.png
22 ms
39082adb44fd4060e16a20c735286ef4.png
22 ms
d6b4a4d753e234723171c5768d12d340.png
22 ms
43019_1125.jpg
22 ms
17747_247.jpg
22 ms
0d2072e073734abd196c76b7f66ed47d.jpg
21 ms
59219_0023.jpg
21 ms
flexslider.css
8 ms
42a452026be1e5ec37e46d5782e688bb.jpg
23 ms
3297af10094a95e43b083e21391c7f0e.jpg
24 ms
5263adca57065b01b831da59485f4bda.jpg
23 ms
275c46ea5babcefd8967ffc9577db8b7.jpg
23 ms
f4d24833472e348dba1e62dcb8916e2b.jpg
22 ms
8683248e9552d44088e18430de88b26e.jpg
22 ms
b1718ed59e406089eff0c3734508f073.jpg
22 ms
0da05745ee6a068c6a29c7ac9d1d01c5.jpg
21 ms
7ff71f2841429de711277fdd5060d504.jpg
22 ms
453f145eae7e0470da93ff506f307166.jpg
21 ms
fd8d12ada9b6478706640d833272923b.jpg
21 ms
4d21bb7dbda18de1ec935e4a211c5a51.jpg
21 ms
0403fb3636af824b3fe1e49f59f6364b.jpg
20 ms
a3ab22cc99ecb5bbbce5c6faf38b6b32.jpg
20 ms
6a900c33117a24160df988b4df2bd089.jpg
20 ms
0f4787c6f96b11bec4e244a1b36e2983.jpg
21 ms
enguard.jpg
3 ms
bgpgoto.jpg
3 ms
autopic.net accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs 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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible 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
[id] attributes on active, focusable elements are not unique
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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>).
autopic.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
autopic.net 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
Tap targets are not sized appropriately
![]()
ZH
![]()
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Autopic.net can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Autopic.net 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.
autopic.net
Open Graph description is not detected on the main page of Autopic. 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: