atlas-guide
Total Declarations
Size
Files size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
14 Heavy selectors This selectors should be simplified
Specifisity | |
---|---|
60 | .atlas-nav>.atlas-nav__item .atlas-nav__item .atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
50 | .atlas-nav>.atlas-nav__item .atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
50 | .atlas-nav .atlas-nav__ln._category.js-collapsed+.atlas-nav__sub-nav |
41 | .atlas-nav .atlas-nav__ln._category.js-collapsed svg |
40 | .atlas-nav>.atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
40 | .js-found .atlas-nav__ln.js-relevant:hover |
40 | .js-found .atlas-nav__ln.js-relevant:focus |
40 | .js-found .atlas-nav__ln.js-relevant:active |
40 | .atlas-stat-digit._uri .atlas-stat-digit__data._display |
40 | .atlas-playground .language-css .token.string |
40 | .atlas-playground .style .token.string |
40 | .atlas-code .language-css .token.string |
40 | .atlas-code .style .token.string |
40 | .atlas-anchor:target+.atlas-title .atlas-title__highlight |
11 Long selectors lists This selectors is potential candidates for simple CSS class
Selectors | |
---|---|
7 |
.atlas-code .token.property, .atlas-code .token.tag, .atlas-code .token.boolean, .atlas-code .token.number, .atlas-code .token.constant, .atlas-code .token.symbol, .atlas-code .token.deleted |
6 |
.atlas-playground .token.selector, .atlas-playground .token.attr-name, .atlas-playground .token.string, .atlas-playground .token.char, .atlas-playground .token.builtin, .atlas-playground .token.inserted |
6 |
.atlas-playground .token.operator, .atlas-playground .token.entity, .atlas-playground .token.url, .atlas-playground .language-css .token.string, .atlas-playground .style .token.string, .atlas-playground .token.variable |
6 |
.atlas-code .token.selector, .atlas-code .token.attr-name, .atlas-code .token.string, .atlas-code .token.char, .atlas-code .token.builtin, .atlas-code .token.inserted |
6 |
h1, h2, h3, h4, h5, h6 |
6 |
.atlas-title_1, .atlas-title_2, .atlas-title_3, .atlas-title_4, .atlas-title_5, .atlas-title_6 |
5 |
.atlas-playground .token.property, .atlas-playground .token.tag, .atlas-playground .token.constant, .atlas-playground .token.symbol, .atlas-playground .token.deleted |
5 |
.atlas-code .token.operator, .atlas-code .token.entity, .atlas-code .token.url, .atlas-code .language-css .token.string, .atlas-code .style .token.string |
5 |
.atlas-title__text, .atlas-p, .atlas-ul, .atlas-ol, .atlas-code |
4 |
.atlas-playground .token.comment, .atlas-playground .token.prolog, .atlas-playground .token.doctype, .atlas-playground .token.cdata |
4 |
.atlas-code .token.comment, .atlas-code .token.prolog, .atlas-code .token.doctype, .atlas-code .token.cdata |
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
6 Heavy rulesets This classes potentially could be changed to single class
Declarations | |
---|---|
21 | .atlas-toc |
20 | .atlas-playground__notifier |
18 | .atlas-stat-header |
18 | .atlas-copier__message |
17 | .atlas-nav__ln |
17 | .atlas-playground__summary |
0 Empty rulesets This selectors should be removed from project
26 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
-
.l-atlas-container.js-aside-panel-hidden .l-atlas-container__aside
-
.l-atlas-container.js-aside-panel-hidden .l-atlas-container__main
-
.js-found .atlas-search__icon
-
.js-found .atlas-search__clear
-
.js-aside-panel-hidden .atlas-aside-ctrl
-
.atlas-aside-resizer-overlay.js-dragging
-
.js-aside-panel-hidden .atlas-aside__header
-
.js-aside-panel-hidden .atlas-aside__footer
-
.js-aside-panel-hidden .atlas-aside__content
-
.atlas-nav__ln.js-current-page
-
.atlas-nav .atlas-nav__ln._category.js-collapsed svg
-
.atlas-nav .atlas-nav__ln._category.js-collapsed+.atlas-nav__sub-nav
-
.js-searching .atlas-nav__ln
-
.js-found .atlas-nav__ln
-
.js-found .atlas-nav__ln.js-relevant
-
.js-found .atlas-nav__ln.js-relevant:hover
-
.js-found .atlas-nav__ln.js-relevant:focus
-
.js-found .atlas-nav__ln.js-relevant:active
-
.js-found .atlas-nav__sub-nav
-
.js-found .atlas-nav__ln._category
-
.js-loading-frame .atlas-loader
-
.atlas-stat-page .js-bar-chart
-
.atlas-stat-page .js-line-chart
-
.atlas-playground__notifier.js-show
-
.atlas-playground.js-opened .atlas-playground__example
-
.atlas-playground.js-opened .atlas-playground__example *
1 Universal selectors Universal selectors could affect performance and encapsulation of components
-
.atlas-playground.js-opened .atlas-playground__example *
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
0 Important rules Important rules could dramatically decrease project maintainability and scalability
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
32 Unique Colors
23 Unique Background Colors
26 Unique Font Sizes
-
Abc
5rem
-
Abc
4rem
-
Abc
3rem
-
Abc
2.441rem
-
Abc
2.2rem
-
Abc
2rem
-
Abc
1.563rem
-
Abc
1.25rem
-
Abc
1.2rem
-
Abc
1rem
-
Abc
inherit
-
Abc
.9375rem
-
Abc
0.9rem
-
Abc
.875rem
-
Abc
0.85em
-
Abc
.8125rem
-
Abc
0.8em
-
Abc
0.8rem
-
Abc
12.75px
-
Abc
.75rem
-
Abc
0.7rem
-
Abc
.6875rem
-
Abc
11px
-
Abc
.625rem
-
Abc
0.6rem
-
Abc
8px
3 Unique Font Families
7 Unique Border Radii
-
.3125rem
-
50%
-
5px
-
3px
-
4px
-
100%
-
0
6 Unique Z Indices
-
0
-
1
-
2
-
5
-
10
-
11
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
-
1.5625rem
-
.875rem
-
1.2
-
1.25rem
-
1
-
2.75rem
-
2.5rem
-
1.5
-
3.75rem
-
25px
-
20px
-
1.6
-
.75rem
-
1.4
-
10px
-
15.625rem
-
5px
-
100%
-
1rem
-
.875rem
-
10px
-
1.125rem
-
.5rem
-
.9375rem
-
50px
-
50%
-
10%
-
25%
-
33.3333333333%
-
100px
-
80%
-
0
-
90px
-
16.6666666667%
-
200px
-
.625rem
-
1.5rem
-
250px
-
18px
-
.75rem
-
.6875rem
-
.1875rem
-
100%
-
1.5625rem
-
1rem
-
.875rem
-
20px
-
1.875rem
-
1.25rem
-
1.125rem
-
1px
-
10px
-
0
-
.625rem
-
5px
-
100px
-
1.5rem
-
90vh
-
8px
-
.75rem
-
.1875rem
-
.9375rem
0 Media Queries Consistency of media queries utilization on the project
dev_atlas-frame.css
Total Declarations
Size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
8 Heavy selectors This selectors should be simplified
Specifisity | |
---|---|
60 | .atlas-nav>.atlas-nav__item .atlas-nav__item .atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
50 | .atlas-nav>.atlas-nav__item .atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
50 | .atlas-nav .atlas-nav__ln._category.js-collapsed+.atlas-nav__sub-nav |
41 | .atlas-nav .atlas-nav__ln._category.js-collapsed svg |
40 | .atlas-nav>.atlas-nav__item .atlas-nav__item>.atlas-nav__ln |
40 | .js-found .atlas-nav__ln.js-relevant:hover |
40 | .js-found .atlas-nav__ln.js-relevant:focus |
40 | .js-found .atlas-nav__ln.js-relevant:active |
0 Long selectors lists This selectors is potential candidates for simple CSS class
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
1 Heavy ruleset This classes potentially could be changed to single class
Declarations | |
---|---|
17 | .atlas-nav__ln |
0 Empty rulesets This selectors should be removed from project
21 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
-
.l-atlas-container.js-aside-panel-hidden .l-atlas-container__aside
-
.l-atlas-container.js-aside-panel-hidden .l-atlas-container__main
-
.js-found .atlas-search__icon
-
.js-found .atlas-search__clear
-
.js-aside-panel-hidden .atlas-aside-ctrl
-
.atlas-aside-resizer-overlay.js-dragging
-
.js-aside-panel-hidden .atlas-aside__header
-
.js-aside-panel-hidden .atlas-aside__footer
-
.js-aside-panel-hidden .atlas-aside__content
-
.atlas-nav__ln.js-current-page
-
.atlas-nav .atlas-nav__ln._category.js-collapsed svg
-
.atlas-nav .atlas-nav__ln._category.js-collapsed+.atlas-nav__sub-nav
-
.js-searching .atlas-nav__ln
-
.js-found .atlas-nav__ln
-
.js-found .atlas-nav__ln.js-relevant
-
.js-found .atlas-nav__ln.js-relevant:hover
-
.js-found .atlas-nav__ln.js-relevant:focus
-
.js-found .atlas-nav__ln.js-relevant:active
-
.js-found .atlas-nav__sub-nav
-
.js-found .atlas-nav__ln._category
-
.js-loading-frame .atlas-loader
0 Universal selectors Universal selectors could affect performance and encapsulation of components
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
1 Important rules Important rules could dramatically decrease project maintainability and scalability
-
display: block
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
7 Unique Colors
3 Unique Background Colors
2 Unique Font Sizes
-
Abc
.8125rem
-
Abc
.625rem
1 Unique Font Family
3 Unique Border Radii
-
.3125rem
-
50%
-
5px
3 Unique Z Indices
-
1
-
2
-
11
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
-
1.5625rem
-
.875rem
-
1.2
-
15.625rem
-
5px
-
100%
-
1rem
-
.875rem
-
10px
-
1.125rem
-
.5rem
-
.9375rem
-
100%
-
1.5625rem
-
1rem
-
.875rem
-
20px
-
1.875rem
-
1.25rem
-
1.125rem
-
1px
0 Media Queries Consistency of media queries utilization on the project
dev_atlas-insights.css
Total Declarations
Size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
1 Heavy selector This selectors should be simplified
Specifisity | |
---|---|
40 | .atlas-stat-digit._uri .atlas-stat-digit__data._display |
0 Long selectors lists This selectors is potential candidates for simple CSS class
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
1 Heavy ruleset This classes potentially could be changed to single class
Declarations | |
---|---|
18 | .atlas-stat-header |
0 Empty rulesets This selectors should be removed from project
2 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
-
.atlas-stat-page .js-bar-chart
-
.atlas-stat-page .js-line-chart
0 Universal selectors Universal selectors could affect performance and encapsulation of components
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
0 Important rules Important rules could dramatically decrease project maintainability and scalability
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
3 Unique Colors
3 Unique Background Colors
15 Unique Font Sizes
-
Abc
5rem
-
Abc
4rem
-
Abc
2.441rem
-
Abc
2rem
-
Abc
1.563rem
-
Abc
1.25rem
-
Abc
1.2rem
-
Abc
1rem
-
Abc
.9375rem
-
Abc
0.9rem
-
Abc
0.8rem
-
Abc
0.7rem
-
Abc
.6875rem
-
Abc
0.6rem
-
Abc
8px
2 Unique Font Families
2 Unique Border Radii
-
3px
-
4px
3 Unique Z Indices
-
1
-
5
-
10
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
-
1.25rem
-
1.2
-
1
-
50px
-
50%
-
10px
-
100%
-
10%
-
25%
-
33.3333333333%
-
100px
-
80%
-
0
-
90px
-
20px
-
10px
-
100%
-
0
0 Media Queries Consistency of media queries utilization on the project
dev_atlas-prism.css
Total Declarations
Size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
4 Heavy selectors This selectors should be simplified
Specifisity | |
---|---|
40 | .atlas-playground .language-css .token.string |
40 | .atlas-playground .style .token.string |
40 | .atlas-code .language-css .token.string |
40 | .atlas-code .style .token.string |
8 Long selectors lists This selectors is potential candidates for simple CSS class
Selectors | |
---|---|
7 |
.atlas-code .token.property, .atlas-code .token.tag, .atlas-code .token.boolean, .atlas-code .token.number, .atlas-code .token.constant, .atlas-code .token.symbol, .atlas-code .token.deleted |
6 |
.atlas-playground .token.selector, .atlas-playground .token.attr-name, .atlas-playground .token.string, .atlas-playground .token.char, .atlas-playground .token.builtin, .atlas-playground .token.inserted |
6 |
.atlas-playground .token.operator, .atlas-playground .token.entity, .atlas-playground .token.url, .atlas-playground .language-css .token.string, .atlas-playground .style .token.string, .atlas-playground .token.variable |
6 |
.atlas-code .token.selector, .atlas-code .token.attr-name, .atlas-code .token.string, .atlas-code .token.char, .atlas-code .token.builtin, .atlas-code .token.inserted |
5 |
.atlas-playground .token.property, .atlas-playground .token.tag, .atlas-playground .token.constant, .atlas-playground .token.symbol, .atlas-playground .token.deleted |
5 |
.atlas-code .token.operator, .atlas-code .token.entity, .atlas-code .token.url, .atlas-code .language-css .token.string, .atlas-code .style .token.string |
4 |
.atlas-playground .token.comment, .atlas-playground .token.prolog, .atlas-playground .token.doctype, .atlas-playground .token.cdata |
4 |
.atlas-code .token.comment, .atlas-code .token.prolog, .atlas-code .token.doctype, .atlas-code .token.cdata |
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
0 Heavy rulesets This classes potentially could be changed to single class
0 Empty rulesets This selectors should be removed from project
0 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
0 Universal selectors Universal selectors could affect performance and encapsulation of components
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
0 Important rules Important rules could dramatically decrease project maintainability and scalability
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
15 Unique Colors
0 Unique Background Colors
0 Unique Font Sizes
0 Unique Font Families
0 Unique Border Radii
0 Unique Z Indices
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
0 Media Queries Consistency of media queries utilization on the project
dev_atlas-style.css
Total Declarations
Size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
0 Heavy selectors This selectors should be simplified
0 Long selectors lists This selectors is potential candidates for simple CSS class
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
0 Heavy rulesets This classes potentially could be changed to single class
0 Empty rulesets This selectors should be removed from project
0 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
0 Universal selectors Universal selectors could affect performance and encapsulation of components
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
2 Important rules Important rules could dramatically decrease project maintainability and scalability
-
animation-play-state: paused
-
animation-play-state: initial
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
4 Unique Colors
4 Unique Background Colors
6 Unique Font Sizes
-
Abc
4rem
-
Abc
2.2rem
-
Abc
2rem
-
Abc
1.563rem
-
Abc
.6875rem
-
Abc
11px
2 Unique Font Families
1 Unique Border Radius
-
100%
0 Unique Z Indices
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
-
1.2
-
1
-
1.25rem
-
16.6666666667%
-
33.3333333333%
-
100%
-
200px
-
.625rem
-
0
-
100px
-
100%
-
1.25rem
-
.625rem
-
5px
-
100px
0 Media Queries Consistency of media queries utilization on the project
dev_atlas.css
Total Declarations
Size
Data URIs Data uri not the best approach to serve data (especially in HTTP2). It blows CSS, make images render blocking resource and it comes with less decoding speed and cache invalidation issues. Consider to avoid this practice.
Selectors and rules
Selectors used
Specificity Graph This is zones that could be hard to overwrite and work with. Zones that could escalate specificity and not scaled well during project lifetime.
1 Heavy selector This selectors should be simplified
Specifisity | |
---|---|
40 | .atlas-anchor:target+.atlas-title .atlas-title__highlight |
3 Long selectors lists This selectors is potential candidates for simple CSS class
Selectors | |
---|---|
6 |
h1, h2, h3, h4, h5, h6 |
6 |
.atlas-title_1, .atlas-title_2, .atlas-title_3, .atlas-title_4, .atlas-title_5, .atlas-title_6 |
5 |
.atlas-title__text, .atlas-p, .atlas-ul, .atlas-ol, .atlas-code |
Ruleset Size This graph show you places with selectors that have 15 or more rules inside
4 Heavy rulesets This classes potentially could be changed to single class
Declarations | |
---|---|
21 | .atlas-toc |
20 | .atlas-playground__notifier |
18 | .atlas-copier__message |
17 | .atlas-playground__summary |
0 Empty rulesets This selectors should be removed from project
3 js-
prefixed selectors
This selectors should not be used for styling, since it SoC violation
-
.atlas-playground__notifier.js-show
-
.atlas-playground.js-opened .atlas-playground__example
-
.atlas-playground.js-opened .atlas-playground__example *
1 Universal selectors Universal selectors could affect performance and encapsulation of components
-
.atlas-playground.js-opened .atlas-playground__example *
0 Id selectors It is bad practice to use IDs as selectors for specificity and reusability reasons
0 Important rules Important rules could dramatically decrease project maintainability and scalability
Consistency
Total vs. Unique Declarations This graph could show how effective code organized and reused over styling properties
14 Unique Colors
17 Unique Background Colors
20 Unique Font Sizes
-
Abc
4rem
-
Abc
3rem
-
Abc
2.441rem
-
Abc
2rem
-
Abc
1.563rem
-
Abc
1.25rem
-
Abc
1.2rem
-
Abc
1rem
-
Abc
inherit
-
Abc
.9375rem
-
Abc
.875rem
-
Abc
0.85em
-
Abc
.8125rem
-
Abc
0.8em
-
Abc
0.8rem
-
Abc
12.75px
-
Abc
.75rem
-
Abc
0.7rem
-
Abc
.6875rem
-
Abc
.625rem
3 Unique Font Families
5 Unique Border Radii
-
3px
-
0
-
5px
-
4px
-
.3125rem
4 Unique Z Indices
-
0
-
1
-
5
-
10
Total vs. Unique Space/Metric Declarations This graph could show how effective code organized and reused over space and metric properties
-
2.75rem
-
2.5rem
-
1.25rem
-
1.5
-
1.2
-
3.75rem
-
25px
-
20px
-
1
-
1.6
-
.75rem
-
1.4
-
.875rem
-
10px
-
0
-
100%
-
.875rem
-
1.5rem
-
250px
-
18px
-
15.625rem
-
50%
-
33.3333333333%
-
.75rem
-
.6875rem
-
.1875rem
-
.9375rem
-
1px
-
.875rem
-
1.5rem
-
90vh
-
8px
-
0
-
1rem
-
.75rem
-
.1875rem
-
.9375rem